Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

add_group_members

Add users to an existing ServiceNow group by specifying group ID and member identifiers to manage group membership and access permissions.

Instructions

Add members to an existing group in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID or sys_id
membersYesList of user sys_ids or usernames to add as members

Implementation Reference

  • The main handler function that implements the add_group_members tool. It iterates over the list of members, resolves usernames to sys_ids using get_user if necessary, and creates sys_user_grmember records via POST requests to the ServiceNow API.
    def add_group_members(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: AddGroupMembersParams,
    ) -> GroupResponse:
        """
        Add members to a group in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for adding members to the group.
    
        Returns:
            Response with the result of the operation.
        """
        api_url = f"{config.api_url}/table/sys_user_grmember"
    
        success = True
        failed_members = []
    
        for member in params.members:
            # Get user ID if username is provided
            user_id = member
            if not member.startswith("sys_id:"):
                user = get_user(config, auth_manager, GetUserParams(user_name=member))
                if not user.get("success"):
                    user = get_user(config, auth_manager, GetUserParams(email=member))
    
                if user.get("success"):
                    user_id = user.get("user", {}).get("sys_id")
                else:
                    success = False
                    failed_members.append(member)
                    continue
    
            # Create group membership
            data = {
                "group": params.group_id,
                "user": user_id,
            }
    
            try:
                response = requests.post(
                    api_url,
                    json=data,
                    headers=auth_manager.get_headers(),
                    timeout=config.timeout,
                )
                response.raise_for_status()
            except requests.RequestException as e:
                logger.error(f"Failed to add member '{member}' to group: {e}")
                success = False
                failed_members.append(member)
    
        if failed_members:
            message = f"Some members could not be added to the group: {', '.join(failed_members)}"
        else:
            message = "All members added to the group successfully"
    
        return GroupResponse(
            success=success,
            message=message,
            group_id=params.group_id,
        )
  • Pydantic BaseModel defining the input schema for the add_group_members tool, including group_id (str) and members (list of str: sys_ids or usernames).
    class AddGroupMembersParams(BaseModel):
        """Parameters for adding members to a group."""
    
        group_id: str = Field(..., description="Group ID or sys_id")
        members: List[str] = Field(
            ..., description="List of user sys_ids or usernames to add as members"
        )
  • Tool registration in the central get_tool_definitions() function's dictionary. Maps the tool name to its handler (aliased import), input schema (AddGroupMembersParams), expected return type, description, and serialization method ('raw_dict').
    "add_group_members": (
        add_group_members_tool,
        AddGroupMembersParams,
        Dict[str, Any],  # Expects dict
        "Add members to an existing group in ServiceNow",
        "raw_dict",
    ),
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Add members' implies a mutation operation, it doesn't disclose permission requirements, whether the operation is idempotent, what happens if members already exist, error conditions, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 waste. It's appropriately sized for a simple tool 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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after adding members (success response, error handling), doesn't mention permission requirements, and provides no behavioral context. The 100% schema coverage helps with parameters, but overall completeness is poor for a write operation.

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?

Schema description coverage is 100%, with both parameters well-documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (group_id and members are clearly defined there). This meets the baseline expectation when schema coverage is complete.

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 action ('Add members') and target resource ('existing group in ServiceNow'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'remove_group_members' beyond the opposite action direction, missing an opportunity for clearer distinction.

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. It doesn't mention prerequisites (like needing an existing group), doesn't specify when to use 'create_group' first, and offers no comparison with sibling tools like 'update_group' which might also manage members.

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