servicenow-mcp-ai

Update ServiceNow record

servicenow_update_record

Idempotent

Update fields on an existing ServiceNow record by table and sys_id, with an optional non-mutating plan preview before applying changes.

Instructions

Update fields on an existing record identified by its sys_id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table": "<table>",
      "sys_id": "<sys_id>",
      "values": "<values>"
    },
    "name": "servicenow_update_record"
  }
}

Input Schema

Name	Required	Description
`apply`	No	true executes; omitted: a non-mutating plan preview (SN_WRITE_MODE=apply executes by default).
`table`	Yes	Table, e.g. 'incident'.
`sys_id`	Yes	Record sys_id.
`values`	Yes	Field name/value pairs to change.
`instance`	No	Profile (default active)
`update_set`	No	In-progress update set (sys_id or exact name) to capture the write in, restored after. Default SN_UPDATE_SET; data rows are never captured.
`inputDisplayValue`	No	Values are display values the instance resolves (sysparm_input_display_value); default false: raw.
`expected_mod_count`	No	sys_mod_count from the plan's apply_with; with apply, a changed record is refused (STALE_RECORD).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.1.1Oct 31, 2026

changedInput schema / properties / update_set / description

Previous value: -"Update set (sys_id or exact name, in progress) to record the write in; switched for it, then restored. Default SN_UPDATE_SET, else unchanged. Data-row tables are not captured."New value: +"In-progress update set (sys_id or exact name) to capture the write in, restored after. Default SN_UPDATE_SET; data rows are never captured."

Changed14 schema fields changedv3.0.0Oct 21, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

changedInput schema / properties / apply / description

Previous value: -"Execute the change. In the default plan mode, omitting this returns a non-mutating before/after preview; set true to apply. SN_WRITE_MODE=apply makes execution the default."New value: +"true executes; omitted: a non-mutating plan preview (SN_WRITE_MODE=apply executes by default)."

addedInput schema / properties / expected_mod_count

Added value: +{
+  "description": "sys_mod_count from the plan's apply_with; with apply, a changed record is refused (STALE_RECORD).",
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / fields

Removed value: -{
-  "additionalProperties": {
-    "type": [
-      "string",
-      "number",
-      "boolean",
-      "null"
-    ]
-  },
-  "description": "Field name/value pairs to change on the record.",
-  "type": "object"
-}

addedInput schema / properties / inputDisplayValue

Added value: +{
+  "description": "Values are display values the instance resolves (sysparm_input_display_value); default false: raw.",
+  "type": "boolean"
+}

changedInput schema / properties / instance / description

Previous value: -"Connection profile to use for this call (default: the active profile). See servicenow_list_instances."New value: +"Profile (default active)"

addedInput schema / properties / instance / maxLength
```
Added value: +128
```

changedInput schema / properties / sys_id / description

Previous value: -"The sys_id of the record to update."New value: +"Record sys_id."

addedInput schema / properties / sys_id / pattern
```
Added value: +"^[A-Za-z0-9_-]{1,32}$"
```

changedInput schema / properties / table / description

Previous value: -"Table name, e.g. 'incident'."New value: +"Table, e.g. 'incident'."

addedInput schema / properties / table / pattern
```
Added value: +"^[A-Za-z0-9_]{1,80}$"
```

addedInput schema / properties / update_set

Added value: +{
+  "description": "Update set (sys_id or exact name, in progress) to record the write in; switched for it, then restored. Default SN_UPDATE_SET, else unchanged. Data-row tables are not captured.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / values

Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean",
+      "null"
+    ]
+  },
+  "description": "Field name/value pairs to change.",
+  "type": "object"
+}

changedInput schema / required

Previous value: -[
-  "table",
-  "sys_id",
-  "fields"
-]New value: +[
+  "table",
+  "sys_id",
+  "values"
+]

First observedv2.0.1Sep 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations declare idempotentHint=true and destructiveHint=false, which is consistent with the text. But the description adds nothing beyond them: it omits the arguably essential behavior that apply is omitted by default (non-mutating plan preview), the STALE_RECORD refusal, and the update-set capture semantics — all of which exist only in the schema and are invisible from the description.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but at one sentence for an eight-parameter mutation tool with a dry-run gate it is under-specified rather than appropriately concise.

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

Completeness3/5

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

The rich schema (100% coverage, apply/expected_mod_count/update_set all explained) carries most of the burden, and there is no output schema to explain. Still, for a write tool the description omits the preview-by-default behavior and concurrency-refusal contract, which an agent should know before invoking.

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 every parameter including apply, expected_mod_count, and update_set is documented in structured form; baseline 3 applies. The description's only parameter-level contribution is naming sys_id and 'fields', which the schema already covers in more detail.

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

Purpose3/5

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

States a specific verb and resource ('update fields on an existing record') and adds the sys_id identifier, so the operation is understandable. However, it does nothing to separate it from sibling servicenow_upsert_record, which also writes fields to a record, leaving the agent to infer the difference from the name alone.

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 when-to-use guidance, no exclusions, no alternatives named. The critical distinction between update and servicenow_upsert_record (and servicenow_create_record for new rows) is never addressed, so an agent cannot use the description to route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.