Firstly it's
controller/action/some-url-segment
Views are but the presentation logic that an action method with a view result returns, typically passing the view a model.
Secondly: There are no code-bind files for ASP.NET MVC Views, this is not web forms.
A possible route on the server side may be defined as follows:
url: "{controller}/{action}/page-{pagenum}"
And this would catch any url such as /admin/getuserlist/page-5
And an action method would receive those url segment params too.
ActionResult GetUserList(int pagenum)
The above gets ActionMethod parameter values from URL segments defined in the route.
You could also pass such values via query string:
/Admin/getuserlist?page=3&pagesize=45
You do not need to modify routes when using query string to pass values.
and a route such as url: {controller}/{action}/
Would happily pass that request to:
ActionResult GetUserList(int page, int pagesize)