Skip to main content
Glama
Xerrion

servicenow-platform-mcp

by Xerrion

record_write

Create, update, or delete a record in ServiceNow. Includes preview mode and script field handling.

Instructions

Create, update, or delete a record. Defaults to preview mode.

Script-bearing tables (Business Rules, Script Includes, widgets, etc.) are not special-cased - script-field discovery happens at runtime via sys_dictionary and the table's super_class chain. script_path loads a local file into the resolved target field; script_field names the destination column when more than one script-bearing field is detected.

Args: action: 'create' | 'update' | 'delete'. table: Target table. Required. sys_id: Required for 'update' and 'delete'. data: JSON string of field values. Required for 'create' and 'update'. script_path: Optional absolute path to a local script file. Content is read (UTF-8, max 1 MB) and stored under the resolved target script field. Path resolved with strict=True; constrained to settings.script_allowed_root. When the resolved field has internal_type == 'xml', the content is validated as well-formed XML before any platform call. script_field: Optional override for the destination script field. When empty (default), the first detected script field is used (child-first, sys_dictionary row order within a table). When set, must match one of the script-bearing fields detected from sys_dictionary; otherwise the call returns a structured error listing the detected fields. Use describe(action='list_script_fields', table=...) to discover script fields for a table. preview: When True (default) returns a preview_token; caller invokes record_apply to commit. When False, write commits immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
tableNo
sys_idNo
dataNo
script_pathNo
script_fieldNo
previewNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description carries full burden. It comprehensively discloses behavior: default preview mode, script-path resolution (strict, max 1 MB, XML validation), field detection via sys_dictionary, error behavior for script_field, and preview token workflow. No contradictions.

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 brief overview followed by an Args block, but it includes technical details (e.g., super_class chain, sys_dictionary row order) that could be streamlined. Still, it is efficient for a complex tool with 7 parameters.

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

Completeness5/5

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

Given the tool's complexity (7 parameters, script handling, preview mode) and the presence of an output schema, the description covers all input-related aspects thoroughly. It explains edge cases like script-field discovery and error handling. The output schema is not detailed, but that is acceptable per rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It provides an 'Args' section that explains each of the 7 parameters in detail, including defaults, requirements, and behavior. This adds significant meaning beyond the bare schema.

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 'Create, update, or delete a record' with a specific verb and resource. It distinguishes from siblings like record_read and record_apply by mentioning preview mode and the need for record_apply to commit. The tool's role as a write operation is unambiguous.

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 context for when to use the script-related parameters and mentions preview mode, but does not explicitly state when to use this tool versus alternatives like record_read or query. However, the tool's purpose is clear from sibling names, so the gap is minor.

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/Xerrion/servicenow-platform-mcp'

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