Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Export Record as XML

export_record_xml

Export any ServiceNow record as unload XML for backup, transfer to another instance, or inclusion in update sets. Uses the .do?UNL endpoint to generate reusable XML.

Instructions

Export a single record from a ServiceNow instance in unload XML format. Uses the /.do?UNL endpoint to generate ServiceNow-native XML that can be imported into another instance or used as a configuration backup.

Common use cases:

  • Backing up a Script Include, Business Rule, or other configuration record

  • Exporting a record to transfer it to another instance

  • Comparing record definitions across instances

  • Generating XML for inclusion in an update set

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias to use. This is the alias configured via `now-sdk auth --add` (e.g., "myinstance", "prod", "test"). The user will typically refer to this by name when saying things like "on my myinstance instance". If not provided, falls back to the SN_AUTH_ALIAS environment variable.
tableYesThe table name of the record to export (e.g., 'sys_script_include', 'sys_script', 'incident', 'sys_ui_page', 'kb_knowledge').
sys_idYesThe sys_id of the record to export.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the UNL endpoint and states the output is ServiceNow-native XML, but does not disclose potential side effects, authentication requirements, or rate limits. The tool is read-only, but that is not explicitly stated.

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 clear opening sentence and bulleted use cases. It is concise but slightly verbose in the first sentence. Overall, it efficiently conveys the tool's purpose without excessive detail.

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?

Given the absence of an output schema, the description does not detail the XML structure, error handling, or required permissions. It provides enough context for basic use but lacks completeness for an agent to fully understand the output format and potential issues.

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?

The input schema already provides clear descriptions for all three parameters (instance, table, sys_id) with 100% coverage. The description adds no additional meaning or constraints beyond what the schema offers, meeting the baseline expectation.

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 explicitly states 'Export a single record... in unload XML format' and lists concrete use cases like backing up, transferring, and comparing records. It clearly distinguishes the tool's purpose from siblings such as import_records_xml.

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 common use cases (backup, transfer, comparison, update set generation), giving clear guidance on when to use the tool. However, it does not explicitly exclude scenarios or mention alternatives beyond the implied opposite (import_records_xml).

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/sonisoft-cnanda/now-sdk-ext-mcp'

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