Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

add_group_members

Add members to a specific group by providing group ID and user sys_ids or usernames, enabling group management via ServiceNow API integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The function implementing the core logic of the 'add_group_members' tool. It resolves user IDs from usernames or emails, then posts to the sys_user_grmember table to add memberships.
    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 (parameters) for the add_group_members tool.
    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"
        )
  • The tool is registered in the central get_tool_definitions() function's dictionary, mapping name to (handler, schema, return_type, description, serialization).
    "add_group_members": (
        add_group_members_tool,
        AddGroupMembersParams,
        Dict[str, Any],  # Expects dict
        "Add members to an existing group in ServiceNow",
        "raw_dict",
    ),
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/echelon-ai-labs/servicenow-mcp'

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