Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

remove_group_members

Remove specified users from a ServiceNow group to manage access permissions and group membership effectively.

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 tool logic: iterates over members, resolves user sys_ids if needed, queries for sys_user_grmember records matching the group and user, and deletes them.
    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: requires group_id (str) and members (list of str, sys_ids or usernames).
    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's dictionary, associating the tool name with its handler (aliased import), params model, 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. While 'Remove' implies a destructive mutation, the description doesn't specify whether this requires special permissions, whether removal is permanent or reversible, what happens if members don't exist, or any rate limits/constraints. It provides minimal behavioral context beyond the basic operation.

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 wasted words. It's appropriately sized for a straightforward tool and gets directly to the point without unnecessary elaboration.

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

Completeness3/5

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

For a destructive mutation tool with no annotations and no output schema, the description is minimally adequate but has significant gaps. It identifies the operation but lacks crucial context about permissions, consequences, error conditions, and what the tool returns. The 100% schema coverage helps, but behavioral transparency remains insufficient.

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%, so the schema already documents both parameters thoroughly. The description doesn't add any additional parameter semantics beyond what's in the schema (e.g., format examples, edge cases, or validation rules). Baseline 3 is appropriate when 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 ('Remove members') and target resource ('from an existing group in ServiceNow'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'update_group' or 'delete_group' which might also affect group membership.

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. There's no mention of prerequisites (like needing admin permissions), when not to use it, or how it differs from related operations like 'update_group' which might also modify membership.

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