Skip to main content
Glama

Bulk update

bulk_update
DestructiveIdempotent

Update multiple records of a resource type in one API call (max 100). Each item must include an "id" field (UUID). 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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesArray of objects to update (max 100). Each must include an "id" field (UUID, from the matching list_ tool) plus the fields to change, which are the fields of the matching single-update tool (resource "work-orders" -> update_work_order).
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 update (max 100). Each must include an \"id\" field (UUID) plus fields to change."New value: +"Array of objects to update (max 100). Each must include an \"id\" field (UUID, from the matching list_ tool) plus the fields to change, which are the fields of the matching single-update tool (resource \"work-orders\" -> update_work_order)."
  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?

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds substantive context the annotations cannot: the 100-item cap, partial-failure semantics ('one failure does not affect others'), per-item return shape, required {resource}:write scope, and that the whole call counts as one rate-limit request. Nothing here contradicts the annotations.

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?

Six short sentences, each carrying distinct operational information, with the core purpose and batch limit front-loaded and the read alternative placed at the end. No filler or restatement 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 destructive bulk mutation with no output schema, the definition covers the item cap, required id, partial-failure behavior, per-item results, authorization scope, and rate-limit accounting. An agent has everything needed to invoke it correctly and interpret the outcome.

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 description coverage is 100%, so both parameters and the per-item 'id' requirement are already documented in the schema. The description largely restates those facts (id must be a UUID, max 100) rather than adding new meaning, so the baseline applies.

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?

States a specific verb and resource ('Update multiple records of a resource type in one API call') plus the batching constraint (max 100), which cleanly separates it from the singular update_<resource> siblings and from bulk_create. An agent can identify the operation and its batched nature 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?

The closing clause gives an explicit when-not and names the alternative for reads ('to read many records use list_<resource> (e.g. list_assets)'). It does not explicitly distinguish itself from bulk_create or from per-resource single-update tools, so the guidance is clear but not exhaustive.

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