servicenow-api

Insert multiple import sets

servicenow_insert_multiple_import_sets

Insert multiple records into a ServiceNow import set by providing the table and data, returning details for each inserted record.

Instructions

Insert multiple records into the specified import set.

:param table: The name of the table associated with the import set. :type table: str :param data: Dictionary containing the field values for multiple new import set records. :type data: dict

:return: Response containing list of parsed Pydantic models with information about the inserted import set records. :rtype: Response

:raises ParameterError: If data or table is not provided. :raises ParameterError: If JSON serialization fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "servicenow_insert_multiple_import_sets"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`table`	No
`import_set_sys_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Oct 19, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: it raises ParameterError when data or table is missing, and when JSON serialization fails, which tells the agent about failure modes. It does not mention permissions, rate limits, or batching limits.

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 docstring leads with the purpose sentence and then uses standard, scannable sections. The redundant :type/:rtype lines add bulk without information, which keeps it out of the top band, but nothing is padded or buried.

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?

There is no output schema, and the description compensates by describing the return: a response containing a list of parsed models with inserted-record information, which is helpful. However, for a three-parameter mutation tool it omits the identity parameter (import_set_sys_id), the shape of batch input, and any prerequisites, leaving the definition only partially complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the burden, but it only documents two of three parameters. The critical import_set_sys_id parameter, which appears to be how the target import set is actually identified, is never mentioned, and the 'specified import set' phrase has no corresponding named input. The data parameter is described as a 'dict' of field values for 'multiple' records, which is semantically confusing without clarifying whether it is a single record payload or a batch.

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 states a specific verb and resource: inserting multiple records into a named import set. That is enough for an agent to know what the tool does, but it never distinguishes itself from the sibling servicenow_insert_import_set (singular), relying on the tool name alone to carry the cardinality difference.

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 when-to-use, when-not-to-use, or alternative guidance at all. The presence of a near-identical single-record sibling (servicenow_insert_import_set) makes the absence of routing guidance a real gap.

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

Deploy Server