Skip to main content
Glama
javerthl

ServiceNow MCP Server

by javerthl

create_user

Create a new user account in ServiceNow by providing required details like username, name, email, and optional information such as department, roles, and contact details.

Instructions

Create a new user in ServiceNow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoWhether the user account is active
departmentNoDepartment the user belongs to
emailYesEmail address of the user
first_nameYesFirst name of the user
last_nameYesLast name of the user
locationNoLocation of the user
managerNoManager of the user (sys_id or username)
mobile_phoneNoMobile phone number of the user
passwordNoPassword for the user account
phoneNoPhone number of the user
rolesNoRoles to assign to the user
titleNoJob title of the user
user_nameYesUsername for the user

Implementation Reference

  • The handler function that executes the create_user tool, building user data and POSTing to ServiceNow sys_user table, with role assignment handling.
    def create_user(
        config: ServerConfig,
        auth_manager: AuthManager,
        params: CreateUserParams,
    ) -> UserResponse:
        """
        Create a new user in ServiceNow.
    
        Args:
            config: Server configuration.
            auth_manager: Authentication manager.
            params: Parameters for creating the user.
    
        Returns:
            Response with the created user details.
        """
        api_url = f"{config.api_url}/table/sys_user"
    
        # Build request data
        data = {
            "user_name": params.user_name,
            "first_name": params.first_name,
            "last_name": params.last_name,
            "email": params.email,
            "active": str(params.active).lower(),
        }
    
        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
    
        # Make request
        try:
            response = requests.post(
                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 and result.get("sys_id"):
                assign_roles_to_user(config, auth_manager, result.get("sys_id"), params.roles)
    
            return UserResponse(
                success=True,
                message="User created successfully",
                user_id=result.get("sys_id"),
                user_name=result.get("user_name"),
            )
    
        except requests.RequestException as e:
            logger.error(f"Failed to create user: {e}")
            return UserResponse(
                success=False,
                message=f"Failed to create user: {str(e)}",
            )
  • Pydantic model defining input parameters for the create_user tool.
    class CreateUserParams(BaseModel):
        """Parameters for creating a user."""
    
        user_name: str = Field(..., description="Username for the user")
        first_name: str = Field(..., description="First name of the user")
        last_name: str = Field(..., description="Last name of the user")
        email: str = Field(..., 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(True, description="Whether the user account is active")
  • Registration of the create_user tool in the tool definitions dictionary, including function, params model, description, and serialization method.
    "create_user": (
        create_user_tool,
        CreateUserParams,
        Dict[str, Any],  # Expects dict
        "Create a new user in ServiceNow",
        "raw_dict",  # Tool returns 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 but only states the action without behavioral details. It doesn't mention whether this is a write operation (implied but not explicit), what permissions are needed, what happens on success/failure, or any side effects like email notifications. For a mutation tool with zero annotation coverage, this is inadequate.

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 and front-loaded with the essential action, making it easy to parse quickly.

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 13 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, authentication requirements, or system-specific behaviors. The context demands more completeness than provided.

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 fully documents all 13 parameters. The description adds no parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 where 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 verb ('Create') and resource ('new user in ServiceNow'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'create_group' or 'create_incident' beyond specifying the resource type.

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 guidance is provided on when to use this tool versus alternatives like 'update_user' or 'get_user', nor does it mention prerequisites, permissions required, or typical use cases. The description only states what it does, not when to use it.

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