servicenow-mcp-ai

Delete ServiceNow record

servicenow_delete_record

Idempotent

Deletes a record from a ServiceNow table using its sys_id, supporting plan preview or apply execution for controlled changes.

Instructions

Delete a record from a table 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>"
    },
    "name": "servicenow_delete_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.
`instance`	No	Profile (default active)
`plan_token`	No	Plan preview token (apply:true)
`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.
`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."

Changed11 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"
+}

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
```

addedInput schema / properties / plan_token

Added value: +{
+  "description": "Plan preview token (apply:true)",
+  "maxLength": 64,
+  "type": "string"
+}

changedInput schema / properties / sys_id / description

Previous value: -"The sys_id of the record to delete."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"
+}

First observedv2.0.1Sep 5, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations only declare idempotentHint=true, so the description carries the burden of disclosing that this is a destructive write, that a call without apply:true returns a non-mutating plan preview rather than deleting, and that update_set/expected_mod_count affect execution. None of that appears in the description text, even though it is critical for a delete operation.

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?

A single front-loaded sentence with zero filler. It is efficient, though the terseness borders on under-specification for a destructive operation.

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 destructive tool with seven parameters, no output schema, and only an idempotentHint annotation, the description omits the single most important behavioral fact: without apply:true the call only produces a plan preview. An agent reading only the description could believe a bare call deletes the record.

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 all seven parameters including apply, plan_token, and expected_mod_count are documented in the schema. The description adds no parameter meaning beyond that, which is the baseline case for full schema coverage.

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 gives a specific verb (delete) plus resource (record from a table) and identifies the key (sys_id), which cleanly separates it from the create/update/upsert siblings. It stops short of naming or contrasting any sibling explicitly, but 'delete' is unambiguous in this CRUD family.

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?

There is no guidance on when to use this versus servicenow_update_record or servicenow_upsert_record, no prerequisites, and no warnings about irreversibility. The agent must infer usage entirely from the name.

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