Skip to main content
Glama
JLKmach

ServiceNow MCP Server

by JLKmach

remove_group_members

Remove users from ServiceNow groups to manage access permissions and maintain accurate team membership by specifying group IDs and member identifiers.

Instructions

Remove members from an existing group in ServiceNow

Input Schema

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

Implementation Reference

  • The core handler function implementing the logic to remove group members by resolving user IDs, querying sys_user_grmember table, and deleting membership records.
    def remove_group_members(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: RemoveGroupMembersParams,
    ) -> GroupResponse:
        """
        Remove members from a group in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for removing members from the group.
    
        Returns:
            Response with the result of the operation.
        """
        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
    
            # Find and delete the group membership
            api_url = f"{config.api_url}/table/sys_user_grmember"
            query_params = {
                "sysparm_query": f"group={params.group_id}^user={user_id}",
                "sysparm_limit": "1",
            }
    
            try:
                # First find the membership record
                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", [])
                if not result:
                    success = False
                    failed_members.append(member)
                    continue
    
                # Then delete the membership record
                membership_id = result[0].get("sys_id")
                delete_url = f"{api_url}/{membership_id}"
    
                response = requests.delete(
                    delete_url,
                    headers=auth_manager.get_headers(),
                    timeout=config.timeout,
                )
                response.raise_for_status()
    
            except requests.RequestException as e:
                logger.error(f"Failed to remove member '{member}' from group: {e}")
                success = False
                failed_members.append(member)
    
        if failed_members:
            message = f"Some members could not be removed from the group: {', '.join(failed_members)}"
        else:
            message = "All members removed from the group successfully"
    
        return GroupResponse(
            success=success,
            message=message,
            group_id=params.group_id,
        )
  • Pydantic BaseModel defining the input schema for the tool: group_id (str) and members (list of str).
    class RemoveGroupMembersParams(BaseModel):
        """Parameters for removing members from 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 remove as members"
        )
  • Tool registration in the central get_tool_definitions() function, associating the tool name with its handler, schema, return type hint, description, and serialization method.
    "remove_group_members": (
        remove_group_members_tool,
        RemoveGroupMembersParams,
        Dict[str, Any],  # Expects dict
        "Remove members from 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 but offers minimal information. It states the tool removes members but doesn't describe what happens upon removal (e.g., access revocation, audit trails), whether the operation is reversible, permission requirements, or error conditions. For a destructive mutation tool, this leaves critical behavioral traits undisclosed.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, with zero redundancy or fluff.

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 (a destructive mutation with 2 required parameters), lack of annotations, and no output schema, the description is insufficiently complete. It doesn't cover behavioral aspects like side effects, permissions, or response format, leaving the agent with significant gaps in understanding how to properly invoke and interpret results from this tool.

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 ('group_id' and 'members') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides (e.g., format examples, constraints, or edge cases). According to guidelines, baseline is 3 when schema coverage is high (>80%) and description adds no extra param info.

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 ('Remove members') and target resource ('from an existing group in ServiceNow'), providing a specific verb+resource combination. It distinguishes itself from sibling tools like 'add_group_members' by specifying removal rather than addition, though it doesn't explicitly contrast with other group-related operations like 'update_group' or 'list_groups'.

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 (e.g., needing an existing group), exclusions (e.g., cannot remove all members), or when to choose this over other group management tools like 'update_group'. The agent must infer usage from the tool name 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/JLKmach/servicenow-mcp'

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