Skip to main content
Glama

bulk_update_items

Update multiple items in a collection simultaneously by specifying a collection name and an array of items with their IDs and fields to update.

Instructions

Update multiple items in a collection at once. Each item must include an id field. Example: {collection: "articles", items: [{id: 1, status: "published"}, {id: 2, status: "published"}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection name
itemsYesArray of items with id and fields to update
Behavior3/5

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

No annotations exist, so the description carries full burden. It discloses the requirement for id fields and shows an example of partial updates, but does not detail idempotency, error handling, or response behavior.

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 two sentences plus an example, front-loaded with the purpose. Every element is necessary and efficiently presented.

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?

While the description is clear enough for basic usage, it lacks information about return values, error handling, or limits, which are important for a bulk mutation tool without an output schema.

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%, but the description adds value by requiring an id field in each item and providing an example that clarifies the structure beyond the generic schema.

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 updates multiple items in a collection, with a specific verb and resource. It effectively distinguishes from sibling tools like bulk_create_items and bulk_delete_items.

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 description provides an example and clarifies that each item must include an id field, but does not explicitly state when to use this tool versus alternatives like update_item. However, the context implies bulk usage.

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/Skeyelab/directus-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server