Skip to main content
Glama

Bulk create

bulk_create

Create multiple records of a resource type in one API call (max 100). Each item is processed independently - one failure does not affect others. Returns per-item results. Requires {resource}:write scope. Counts as 1 request for rate limiting. Writes only: to read many records use list_ (e.g. list_assets), which returns every page.

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": {
      "resource": "<resource>",
      "items": "<items>"
    },
    "name": "bulk_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesArray of objects to create (max 100). Each object takes the fields of the matching single-create tool (resource "work-orders" -> create_work_order), including the fields it marks (required). Required fields for common resources: assets name; work-orders title; work-requests title; sites name; buildings name, site_id; locations name, building_id; systems, system-groups, system-classes, vendors name; pm-schedules title; projects name, start_date; project-tasks project_id, title; expenses project_id, description, amount, expense_date; infrastructure-assets network_id, feature_type, geometry.
resourceYesResource type (e.g. "assets", "work-orders")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / items / description
      Previous value: -"Array of objects to create (max 100). Each object uses the same fields as the single-create endpoint for that resource."New value: +"Array of objects to create (max 100). Each object takes the fields of the matching single-create tool (resource \"work-orders\" -> create_work_order), including the fields it marks (required). Required fields for common resources: assets name; work-orders title; work-requests title; sites name; buildings name, site_id; locations name, building_id; systems, system-groups, system-classes, vendors name; pm-schedules title; projects name, start_date; project-tasks project_id, title; expenses project_id, description, amount, expense_date; infrastructure-assets network_id, feature_type, geometry."
  2. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / items / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / items / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  4. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / items / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent), the description discloses the 100-item cap, per-item independent processing so one failure does not abort the batch, per-item return results, the required {resource}:write scope, and that the whole call counts as 1 toward rate limiting. That is high-value operational context an agent cannot infer from structured fields.

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 compact sentences, front-loaded with the action and cap, then failure semantics, then auth and rate-limit facts, then the read alternative. No filler and no repetition of the title.

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?

For a 2-parameter write tool with no output schema, it covers partial-failure behavior, response shape (per-item results), permission requirements, throttling cost, and the read-path alternative. Nothing material is missing for correct invocation.

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?

Schema coverage is 100% and the schema already enumerates required fields per resource and the maxItems/minItems bounds, so it carries most of the weight. The description restates the max-100 limit and indexes the item shape back to the matching single-create tool, which is mildly additive but not new semantics.

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?

"Create multiple records of a resource type in one API call (max 100)" gives a specific verb, resource scope, and batch bound. It is clearly separable from the singular create_* siblings and from bulk_update, and the trailing sentence pins it as the write path.

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 explicitly routes the read-many case to list_<resource> with a concrete example (list_assets), which is exactly the choice an agent can get wrong. It stops short of saying when to use this versus looping singular create_* calls, so the batch-vs-single comparison is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources