Skip to main content
Glama
echelon-ai-labs

ServiceNow MCP Server

update_user

Modify user details such as active status, department, email, name, location, manager, phone, roles, and password in ServiceNow using the specified user ID or sys_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Implementation Reference

  • The handler function that executes the update_user tool, sending a PATCH request to ServiceNow's sys_user table to update user details and optionally assign roles.
    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/parameters for the update_user tool.
    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")
  • Registers the update_user tool in the central tool_definitions dictionary used by the MCP server, mapping the name to its handler, schema, return type, description, and serialization method.
    "update_user": (
        update_user_tool,
        UpdateUserParams,
        Dict[str, Any],  # Expects dict
        "Update an existing user in ServiceNow",
        "raw_dict",
    ),
  • Imports the update_user function aliased as update_user_tool for use in tool registration.
    from servicenow_mcp.tools.user_tools import (
        update_user as update_user_tool,
    )
  • Re-exports the update_user function from user_tools.py for convenient access across the tools module.
    from servicenow_mcp.tools.user_tools import (
        create_user,
        update_user,
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