Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Batch Create Records

batch_create_records

Create multiple records across ServiceNow tables in a single batch call, supporting sequential operations with variable references to link records across tables.

Instructions

Create multiple records across one or more ServiceNow tables in a single batch. Operations execute sequentially, supporting variable references between them: use saveAs to name an operation's result sys_id, then reference it in later operations with ${name} in data values.

Example: Create a parent record with saveAs='parent', then create a child record with caller_id set to '${parent}'.

IMPORTANT: This creates records on the ServiceNow instance. Review the operations before executing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
operationsYesOrdered list of create operations to execute.
transactionNoWhen true (default), stops on first error. When false, continues past errors.
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses sequential execution, variable referencing via saveAs, and error handling via the transaction parameter. This adds significant behavioral context beyond a simple 'create' statement, though it could mention rollback behavior or idempotency.

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

Conciseness5/5

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

The description is concise and front-loaded: purpose in first sentence, key feature and example next, important warning last. No unnecessary words, well-structured for quick comprehension.

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 3 parameters, 100% schema coverage, no output schema, and sibling context, the description covers core behavior (sequential execution, variable references, error handling). It lacks mention of maximum batch size or success response format, but these are not critical for tool selection.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by explaining how saveAs and variable references work, providing an example, and clarifying the transaction parameter's effect. This goes beyond the schema definitions.

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 the tool creates multiple records across tables in a batch, distinguishing it from siblings like batch_update_records or single-record creation tools. It specifies verb (create), resource (multiple records), and scope (across tables).

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 warns that records are created and advises reviewing operations, but does not explicitly guide when to use this tool versus alternatives (e.g., single record creation or other batch tools). It lacks clear when-to-use or when-not-to-use context.

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