Skip to main content
Glama
vparlapalli490

ServiceNow MCP Server

update_user

Modify user details in ServiceNow by updating information such as name, email, department, roles, and account status for existing users.

Instructions

Update an existing user in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID or sys_id to update
user_nameNoUsername for the user
first_nameNoFirst name of the user
last_nameNoLast name of the user
emailNoEmail address of the user
titleNoJob title of the user
departmentNoDepartment the user belongs to
managerNoManager of the user (sys_id or username)
rolesNoRoles to assign to the user
phoneNoPhone number of the user
mobile_phoneNoMobile phone number of the user
locationNoLocation of the user
passwordNoPassword for the user account
activeNoWhether the user account is active

Implementation Reference

  • The core handler function that builds the update payload and sends a PATCH request to the ServiceNow sys_user table API endpoint. Handles optional fields, role assignments, and error responses.
    def update_user(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: UpdateUserParams,
    ) -> UserResponse:
        """
        Update an existing user in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for updating the user.
    
        Returns:
            Response with the updated user details.
        """
        api_url = f"{config.api_url}/table/sys_user/{params.user_id}"
    
        # Build request data
        data = {}
        if params.user_name:
            data["user_name"] = params.user_name
        if params.first_name:
            data["first_name"] = params.first_name
        if params.last_name:
            data["last_name"] = params.last_name
        if params.email:
            data["email"] = params.email
        if params.title:
            data["title"] = params.title
        if params.department:
            data["department"] = params.department
        if params.manager:
            data["manager"] = params.manager
        if params.phone:
            data["phone"] = params.phone
        if params.mobile_phone:
            data["mobile_phone"] = params.mobile_phone
        if params.location:
            data["location"] = params.location
        if params.password:
            data["user_password"] = params.password
        if params.active is not None:
            data["active"] = str(params.active).lower()
    
        # Make request
        try:
            response = requests.patch(
                api_url,
                json=data,
                headers=auth_manager.get_headers(),
                timeout=config.timeout,
            )
            response.raise_for_status()
    
            result = response.json().get("result", {})
    
            # Handle role assignments if provided
            if params.roles:
                assign_roles_to_user(config, auth_manager, params.user_id, params.roles)
    
            return UserResponse(
                success=True,
                message="User updated successfully",
                user_id=result.get("sys_id"),
                user_name=result.get("user_name"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to update user: {e}")
            return UserResponse(
                success=False,
                message=f"Failed to update user: {str(e)}",
            )
  • Pydantic BaseModel defining the input schema for the update_user tool, including all optional fields for user updates.
    class UpdateUserParams(BaseModel):
        """Parameters for updating a user."""
    
        user_id: str = Field(..., description="User ID or sys_id to update")
        user_name: Optional[str] = Field(None, description="Username for the user")
        first_name: Optional[str] = Field(None, description="First name of the user")
        last_name: Optional[str] = Field(None, description="Last name of the user")
        email: Optional[str] = Field(None, description="Email address of the user")
        title: Optional[str] = Field(None, description="Job title of the user")
        department: Optional[str] = Field(None, description="Department the user belongs to")
        manager: Optional[str] = Field(None, description="Manager of the user (sys_id or username)")
        roles: Optional[List[str]] = Field(None, description="Roles to assign to the user")
        phone: Optional[str] = Field(None, description="Phone number of the user")
        mobile_phone: Optional[str] = Field(None, description="Mobile phone number of the user")
        location: Optional[str] = Field(None, description="Location of the user")
        password: Optional[str] = Field(None, description="Password for the user account")
        active: Optional[bool] = Field(None, description="Whether the user account is active")
  • Tool registration in get_tool_definitions() dictionary, associating the aliased handler function, input schema, return type hint, description, and serialization method.
    "update_user": (
        update_user_tool,
        UpdateUserParams,
        Dict[str, Any],  # Expects dict
        "Update an existing user in ServiceNow",
        "raw_dict",
    ),
  • Import statement in tools/__init__.py that exposes the update_user function for use across the module.
    from servicenow_mcp.tools.user_tools import (
        create_user,
        update_user,
        get_user,
        list_users,
        create_group,
        update_group,
        add_group_members,
        remove_group_members,
        list_groups,
    )
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 'Update' implies a mutation operation, the description doesn't mention permission requirements, whether changes are reversible, what happens to unspecified fields, or typical response patterns. This leaves significant gaps for a mutation tool.

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 states the core purpose without unnecessary words. It's appropriately sized for a tool with comprehensive schema documentation and gets straight to the point.

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 14 parameters and no annotations or output schema, the description is inadequate. It doesn't address behavioral aspects like permissions, side effects, or response format, leaving the agent with insufficient context to use the tool effectively beyond basic parameter passing.

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?

The schema description coverage is 100%, with each parameter well-documented in the schema itself. The description adds no additional parameter information beyond what's already in the structured data, so it meets the baseline expectation but doesn't provide extra value.

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 ('Update') and target ('an existing user in ServiceNow'), making the purpose immediately understandable. However, it doesn't differentiate this from sibling tools like 'create_user' or 'get_user' beyond the obvious verb difference, which prevents a perfect score.

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 like 'create_user' or 'get_user', nor does it mention prerequisites (e.g., needing the user's ID). It simply states what the tool does without context about appropriate usage scenarios.

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