Skip to main content
Glama

bulk_action

Execute bulk create, update, delete, publish, or unpublish on multiple content entries with per-entry error handling so individual failures do not abort the entire batch.

Instructions

Execute a bulk operation (create, update, delete, publish, or unpublish) on multiple content entries. Processes each entry sequentially with per-entry error handling so individual failures do not abort the entire batch. Returns a detailed summary showing successes, failures, and error messages for each entry. Use this for batch imports, migrations, or mass status changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe bulk operation to perform. Must be one of: 'create', 'update', 'delete', 'publish', or 'unpublish'. Each action expects different entry data formats.
entriesYesJSON array of entry objects. Format depends on the action: - create: [{"title": "A", ...}, {"title": "B", ...}] - update: [{"id": 1, "data": {"title": "Updated"}}, ...] - delete: [{"id": 1}, {"id": 2}, ...] or [1, 2, 3] - publish: [{"id": 1}, {"id": 2}, ...] or [1, 2, 3] - unpublish: [{"id": 1}, {"id": 2}, ...] or [1, 2, 3]
content_typeYesPlural API ID of the content type (e.g., 'articles', 'products')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds sequential processing, per-entry error handling to prevent batch aborts, and return summary details. These go beyond annotations (readOnlyHint, destructiveHint, openWorldHint) providing crucial behavioral insight.

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?

Three sentences: first defines purpose, second adds behavioral details, third gives usage guidance. No redundancy, front-loaded with key information.

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?

Adequately covers what the tool does and how it behaves. Missing potential constraints like batch size limits or idempotency, but output schema and high schema coverage compensate.

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 covers 100% of parameter semantics with detailed descriptions and format examples. Description does not add significant new information about parameters beyond what schema provides.

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 it executes bulk operations (create, update, delete, publish, unpublish) on multiple content entries, explicitly contrasting with single-entry sibling tools.

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?

Explicitly recommends use for batch imports, migrations, or mass status changes. Lacks direct 'when not to use' but sibling tools provide enough context to infer.

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/alex2zimmermann-ux/strapi-mcp'

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