Skip to main content
Glama

Update ServiceNow Record

servicenow_update_record

Update fields on an existing ServiceNow record by sys_id, modifying only the specified values without overwriting other data.

Instructions

Update fields on an existing ServiceNow record by sys_id (PATCH — only specified fields are changed).

Args:

  • table (string): Table name

  • sys_id (string): 32-character sys_id of the record to update

  • data (object): Fields to update with their new values

  • response_format: Output format

Returns: The updated record

Examples:

  • Close a problem → table="problem", sys_id="...", data={"state":"4"}

  • Reassign a task → table="task", sys_id="...", data={"assigned_to":"user_sys_id","assignment_group":"group_sys_id"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesFields to update with new values
tableYesServiceNow table name (e.g., incident, change_request, sys_user)
sys_idYesServiceNow sys_id (32-character GUID) of the record
response_formatNoOutput format: 'markdown' (default) for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already indicate a mutating (readOnlyHint=false) and non-destructive (destructiveHint=false) operation. The description adds the crucial detail that only specified fields are changed (PATCH semantics), and explicitly mentions the return value. This goes beyond the structured annotations without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a concise lead sentence, a bulleted Args list, a Returns line, and two illustrative examples. It is appropriately sized and front-loaded, with no redundant content; each section earns its place.

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 4 parameters, high schema coverage, and no output schema, the description provides sufficient context: the update semantics, the return value, and typical use cases. It does not over-explain but is complete enough for an agent to select and invoke the tool correctly.

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 coverage is 100%, so the schema documents all parameters. The description adds example values for key parameters (e.g., data={"state":"4"}) that illustrate usage but does not redefine parameter semantics. This meets the baseline for high schema coverage with marginal additional value.

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 a specific verb ('Update') and resource ('existing ServiceNow record by sys_id') and specifies the HTTP method (PATCH). It distinguishes the generic update tool from specialized siblings like update_incident and update_change by focusing on arbitrary table/sys_id combinations. Examples reinforce the purpose.

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

Usage Guidelines3/5

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

The description implies usage through the PATCH semantics and examples (e.g., closing a problem, reassigning a task), but it does not explicitly state when to prefer this generic tool over specialized siblings like servicenow_update_incident or servicenow_update_change. There is no mention of exclusions or alternatives.

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/kylburns89/servicenow-mcp-server'

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