Skip to main content
Glama

batch_tasks

Execute multiple task update or move operations atomically in a single call. All operations succeed or none do.

Instructions

Execute multiple task operations atomically in a single call.

operations is a list of operation objects. Each must have an op field ("update" or "move") and a task_id.

Update operations accept the same fields as update_task (title, description, status, labels, etc.) at the top level alongside op and task_id.

Move operations accept new_parent_id (UUID or null for root) and an optional position (insertion index).

All operations succeed or none do (all-or-nothing). On success returns {"tasks": [...]}, the list of all modified tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses atomicity (all-or-nothing) and the return format. It details operation structure for both update and move. However, it does not cover error handling, permission checks, or edge cases.

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 well-structured, with a concise opening sentence summarizing the purpose, followed by bullet-like explanations. Every sentence adds value without redundancy.

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?

The description covers the main aspects: operation types, atomicity, return format. However, it lacks details on validation, error responses, batch size limits, and whether operations can be mixed. Given the complexity and presence of an output schema, it is fairly complete but could be more thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates. It explains the operations array structure, required op and task_id, and the different fields for update vs move. It also references update_task for allowed fields. This adds significant meaning beyond the bare 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's purpose: executing multiple task operations atomically. It specifies the verb 'execute multiple task operations' and the resource 'tasks'. It distinguishes from sibling tools like update_task and move_task by batching operations.

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 explains when to use the tool: for multiple atomic operations. It references individual tools (update_task) for operation fields. It does not explicitly state when not to use it, but the context of batch vs individual is clear.

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/Circuit-Stitch/defernowork-mcp'

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