Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

list_groups

Retrieve and filter ServiceNow groups by active status, type, or search terms in name/description fields, with pagination controls for large datasets.

Instructions

List groups from ServiceNow with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoFilter by active status
limitNoMaximum number of groups to return
offsetNoOffset for pagination
queryNoCase-insensitive search term that matches against group name or description fields. Uses ServiceNow's LIKE operator for partial matching.
typeNoFilter by group type

Implementation Reference

  • The core handler function for the 'list_groups' tool. It constructs a query to the ServiceNow 'sys_user_group' table API, applies filters for limit, offset, active status, type, and search query, fetches the data, and returns a structured response with groups list.
    def list_groups(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: ListGroupsParams,
    ) -> dict:
        """
        List groups from ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for listing groups.
    
        Returns:
            Dictionary containing list of groups.
        """
        api_url = f"{config.api_url}/table/sys_user_group"
        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.type:
            query_parts.append(f"type={params.type}")
        if params.query:
            query_parts.append(f"^nameLIKE{params.query}^ORdescriptionLIKE{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)} groups",
                "groups": result,
                "count": len(result),
            }
    
        except requests.RequestException as e:
            logger.error(f"Failed to list groups: {e}")
            return {"success": False, "message": f"Failed to list groups: {str(e)}"}
  • Pydantic model defining the input parameters for the list_groups tool, including pagination (limit, offset), filters (active, query, type).
    class ListGroupsParams(BaseModel):
        """Parameters for listing groups."""
    
        limit: int = Field(10, description="Maximum number of groups to return")
        offset: int = Field(0, description="Offset for pagination")
        active: Optional[bool] = Field(None, description="Filter by active status")
        query: Optional[str] = Field(
            None,
            description="Case-insensitive search term that matches against group name or description fields. Uses ServiceNow's LIKE operator for partial matching.",
        )
        type: Optional[str] = Field(None, description="Filter by group type")
  • Tool registration entry in get_tool_definitions() dictionary, mapping 'list_groups' to its handler (list_groups_tool), schema (ListGroupsParams), return type hint, description, and serialization method ('raw_dict').
    "list_groups": (
        list_groups_tool,
        ListGroupsParams,
        Dict[str, Any],  # Expects dict
        "List groups from ServiceNow with optional filtering",
        "raw_dict",
    ),
  • Re-export of list_groups function from user_tools in the tools package __init__.py for easy access.
    from servicenow_mcp.tools.user_tools import (
        create_user,
        update_user,
        get_user,
        list_users,
        create_group,
        update_group,
        add_group_members,
        remove_group_members,
        list_groups,
    )
  • Import alias for the list_groups handler as list_groups_tool, used in tool registration.
        list_groups as list_groups_tool,
    )
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it's a list operation with filtering, implying it's read-only, but doesn't disclose behavioral traits like pagination behavior (implied by offset/limit in schema but not described), rate limits, authentication needs, or what happens with large result sets. The description is minimal and lacks critical operational context.

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 that front-loads the core purpose ('List groups from ServiceNow') and adds a key feature ('with optional filtering'). There is no wasted verbiage, making it appropriately sized for its function.

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 complexity (a list operation with 5 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances like how filtering interacts with pagination. For a tool with no structured output documentation, more descriptive context is needed.

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 schema description coverage is 100%, so all parameters are documented in the schema. The description adds no additional meaning beyond mentioning 'optional filtering', which is already covered by the schema's parameter descriptions. This meets the baseline of 3 where the schema does the heavy lifting.

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 clearly states the verb ('List') and resource ('groups from ServiceNow'), making the purpose evident. It also mentions 'optional filtering' which adds specificity. However, it doesn't explicitly differentiate from sibling tools like 'list_users' or 'list_workflows' beyond the resource type.

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 many sibling list tools (e.g., list_users, list_incidents), there's no indication of context, prerequisites, or exclusions. The mention of 'optional filtering' is a feature hint, not usage guidance.

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