Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

add_group_members

Add users to an existing ServiceNow group by specifying group ID and member usernames or sys_ids. This tool manages group membership for access control and collaboration.

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 core handler function that adds users to a group by resolving user IDs and creating sys_user_grmember records via 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 model defining the input parameters for the add_group_members tool: group_id and list of members.
    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"
        )
  • Registration of the add_group_members tool in the central tool definitions dictionary, mapping name to function, schema, return type, description, and serialization method.
    "add_group_members": (
        add_group_members_tool,
        AddGroupMembersParams,
        Dict[str, Any],  # Expects dict
        "Add members to an existing group in ServiceNow",
        "raw_dict",
    ),
  • Import of add_group_members function from user_tools.py into the tools namespace.
    add_group_members,
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. It states the tool adds members but lacks behavioral details: no mention of required permissions, whether the operation is idempotent (e.g., if members already exist), error conditions (e.g., invalid group_id), or what happens on success (e.g., confirmation message). For a mutation tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core purpose and appropriately sized for a straightforward tool, earning its place without redundancy.

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 (mutation operation), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, idempotency, or response format, leaving gaps for an AI agent to invoke it correctly. It should do more to compensate for missing structured data.

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 (group_id as 'Group ID or sys_id', members as 'List of user sys_ids or usernames'). The description adds no additional parameter semantics beyond what the schema provides, so baseline 3 is appropriate as 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 action ('Add members') and target resource ('to an existing group in ServiceNow'), providing specific verb+resource. It distinguishes from sibling 'create_group' (creation vs. modification) and 'remove_group_members' (add vs. remove), though not explicitly named. It's not a tautology as it elaborates beyond the tool name.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for adding members to existing groups, but doesn't mention prerequisites (e.g., group must exist), exclusions, or compare with other member-management tools like 'remove_group_members'. Usage is inferred from the purpose alone.

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/vparlapalli490/MCP'

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