Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_users

Retrieve user records from ServiceNow with filtering options for active status, department, and search queries to manage user information effectively.

Instructions

List users in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoFilter by active status
departmentNoFilter by department
limitNoMaximum number of users to return
offsetNoOffset for pagination
queryNoCase-insensitive search term that matches against name, username, or email fields. Uses ServiceNow's LIKE operator for partial matching.

Implementation Reference

  • Implementation of the list_users tool handler, which queries the ServiceNow sys_user table API with pagination, filtering by active status, department, and search query.
    def list_users(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListUsersParams,
    ) -> dict:
        """
        List users from ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for listing users.
    
        Returns:
            Dictionary containing list of users.
        """
        api_url = f"{config.api_url}/table/sys_user"
        query_params = {
            "sysparm_limit": str(params.limit),
            "sysparm_offset": str(params.offset),
            "sysparm_display_value": "true",
        }
    
        # Build query
        query_parts = []
        if params.active is not None:
            query_parts.append(f"active={str(params.active).lower()}")
        if params.department:
            query_parts.append(f"department={params.department}")
        if params.query:
            query_parts.append(
                f"^nameLIKE{params.query}^ORuser_nameLIKE{params.query}^ORemailLIKE{params.query}"
            )
    
        if query_parts:
            query_params["sysparm_query"] = "^".join(query_parts)
    
        # Make request
        try:
            response = requests.get(
                api_url,
                params=query_params,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", [])
    
            return {
                "success": True,
                "message": f"Found {len(result)} users",
                "users": result,
                "count": len(result),
            }
    
        except requests.RequestException as e:
            logger.error(f"Failed to list users: {e}")
            return {"success": False, "message": f"Failed to list users: {str(e)}"}
  • Pydantic schema for input parameters to the list_users tool, including pagination and filtering options.
    class ListUsersParams(BaseModel):
        """Parameters for listing users."""
    
        limit: int = Field(10, description="Maximum number of users to return")
        offset: int = Field(0, description="Offset for pagination")
        active: Optional[bool] = Field(None, description="Filter by active status")
        department: Optional[str] = Field(None, description="Filter by department")
        query: Optional[str] = Field(
            None,
            description="Case-insensitive search term that matches against name, username, or email fields. Uses ServiceNow's LIKE operator for partial matching.",
        )
  • Registration of the list_users tool in the central tool_definitions dictionary used by the MCP server, mapping name to function, params schema, description, etc.
    "list_users": (
        list_users_tool,
        ListUsersParams,
        Dict[str, Any],  # Expects dict
        "List users in ServiceNow",
        "raw_dict",
    ),
  • Re-export of list_users function in tools package __init__ for easy import.
    list_users,
  • Inclusion of list_users in the __all__ list for the tools package.
    "list_users",
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'List users' implies a read-only operation, but it doesn't mention pagination behavior (implied by offset/limit parameters), authentication requirements, rate limits, or what fields are returned. This leaves significant gaps for a tool with 5 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a straightforward list operation and front-loads the essential information without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (5 parameters, no output schema, no annotations), the description is inadequate. It doesn't explain return format, pagination behavior, or how parameters interact (e.g., query vs. department filtering). For a list tool with multiple filtering options, more context is needed to help the agent use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no parameter information beyond what's already in the schema, which has 100% coverage with clear descriptions for all 5 parameters (active, department, limit, offset, query). This meets the baseline of 3 since the schema does the heavy lifting, but the description provides no additional context about parameter interactions or usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List users in ServiceNow' clearly states the verb ('List') and resource ('users'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_user' or 'create_user' beyond the basic action, which prevents a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get_user' (likely for retrieving a single user) and 'create_user', the agent receives no explicit or implied direction about appropriate contexts or exclusions for this list operation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/javerthl/servicenow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server