Skip to main content
Glama

bulk_create_records

Create many records in one table with a single call, track each created sys_id, and return a rollback token. Enable rollback_on_error for all-or-nothing batches or dry_run to preview payloads.

Instructions

Create many records in one table in a single call, tracking every created sys_id and returning a rollback_token. With rollback_on_error=true, a mid-way failure deletes everything already created so the batch is all-or-nothing. Supports dry_run. Requires WRITE_ENABLED=true.

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>",
      "records": "<records>"
    },
    "name": "bulk_create_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
tableYesTarget table
dry_runNoPreview the resolved payloads without creating anything
recordsYesArray of field key-value objects to create
rollback_on_errorNoIf a create fails, delete the ones already created (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. Addedv4.9.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the key behavioral traits: per-record sys_id tracking, a returned rollback_token, and that rollback_on_error deletes already-created records on mid-way failure. The conditional deletion is opt-in and consistent with destructiveHint=false at default, so there is no contradiction. It leaves open what the caller receives on partial failure when rollback is not enabled, and any batch-size limits.

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?

Four dense sentences, purpose first, then failure semantics, then modes, then the prerequisite. Nothing is repeated from the schema and every sentence carries information an agent needs before invoking.

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?

For a bulk-mutation tool with no output schema, the definition covers return values (sys_ids, rollback_token, job_id) and the safety modes well. Minor gaps remain around partial-failure reporting without rollback and any practical limits on the records array.

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 the baseline is 3, but the description adds real meaning on top: rollback_on_error is framed as all-or-nothing semantics and dry_run as payload preview rather than a silent no-op. The async/job_id mechanics are left entirely to the schema's own parameter description.

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 opens with a specific verb and resource ("Create many records in one table in a single call") and immediately clarifies the bulk scope, which separates it from the many single-record create_* siblings. It also states concrete outputs (sys_ids, rollback_token), so an agent knows exactly what the tool does without opening the schema.

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?

It gives clear conditions for its modes: use rollback_on_error=true for all-or-nothing batches, dry_run for preview, and it states the WRITE_ENABLED=true prerequisite. It does not explicitly contrast with single-record creation or say when a bulk call is the wrong choice, so it stops short of a full when/when-not statement.

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

Deploy Server

Other Tools