Skip to main content
Glama

sn_create_user

Create a ServiceNow user with standard fields, optional roles, and group membership. Handles common mistakes like username generation and default active status.

Instructions

Create a ServiceNow user (sys_user) with all standard fields, optional roles, and optional group membership.

Handles the fields that developers most commonly miss or set incorrectly:

  • Generates a valid user_name if not provided

  • Sets active=true by default

  • Optionally assigns roles directly on the user record

  • Optionally adds the user to one or more groups in one call

Returns the new user's sys_id plus links to role and group records created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameYesFirst name
last_nameYesLast name
emailYesEmail address (used for notifications)
user_nameNoLogin username — auto-generated from first.last if not provided
titleNoJob title
departmentNoDepartment name or sys_id
managerNoManager username, email, or sys_id
phoneNoBusiness phone number
mobile_phoneNoMobile phone number
locationNoLocation name or sys_id
time_zoneNoe.g. "America/New_York"
date_formatNoe.g. "MM/dd/yyyy"
languageNoLanguage code (default: en)en
passwordNoInitial password. If omitted, user must reset on first login.
activeNo
vipNoMark as VIP (affects SLA)
rolesNoRole names to assign (e.g. ["itil","catalog"])
groupsNoGroup names or sys_ids to add the user to
extra_fieldsNoAny additional sys_user fields
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and discloses key behaviors: auto-generating user_name, setting active=true, assigning roles/groups in one call, and return value (sys_id plus links). However, it does not mention prerequisites (e.g., roles must exist) or safety considerations like authentication requirements.

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 efficiently structured: a clear purpose sentence, a bullet list of key behaviors, and a return statement. Every sentence adds value without redundancy, appropriate for 19 parameters.

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

Completeness4/5

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

Given no output schema and 19 parameters including a nested object, the description covers the main use case, common pitfalls, and return value. It lacks explicit guidance on extra_fields usage or prerequisites for roles/groups, but schema descriptions fill most gaps.

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 95% (high), so baseline is 3. The description echoes schema info (auto-generation, defaults) but adds little new meaning beyond emphasizing 'commonly missed fields'. It does not detail format expectations for roles/groups beyond the schema's array of strings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'create', the resource 'ServiceNow user (sys_user)', and the scope 'with all standard fields, optional roles, and optional group membership'. It differentiates from sibling tools like sn_create (generic) and sn_create_group by specifying the exact record type and included features.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for using the tool (creating a user with optional roles/groups) but does not explicitly mention when not to use it or name alternatives. It implies comprehensive coverage but lacks exclusions like 'if you only need a user without roles, consider sn_create'.

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/pinnintisagarSB/ServiceNow-Dev-MCP'

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