Skip to main content
Glama

board_bulk_update_tasks

Update multiple tasks in one call: move to a project, change status, priority, or agent. All tasks are validated together; if any fails, no updates are applied.

Instructions

Apply the same update to multiple tasks in one call. Useful for consolidation (move N tasks to a different project) or bulk status/priority/agent changes. All tasks are validated first — if any task is missing, NO tasks are updated (all-or-nothing). Activity log entries are written per task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idsYesTask IDs to update (1-100)
project_idNoMove all listed tasks to this project. Target project must exist.
statusNoNew status for all listed tasks
priorityNoNew priority for all listed tasks
assigned_agentNoNew agent assignment for all listed tasks (empty string to unassign)
Behavior4/5

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

Discloses all-or-nothing validation and per-task activity logging. No annotations exist, so description carries full burden. Could mention authorization or idempotency.

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, no fluff. Front-loaded with purpose and use cases.

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?

Covers purpose, behavior, and key constraint. No output schema, so missing return details. Missing permission or error handling info, but acceptable for bulk tool.

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 all parameters with descriptions. Description adds overall semantics (same update applied to all) but does not deepen individual parameter meaning beyond 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?

Clearly states 'Apply the same update to multiple tasks' and gives specific use cases (consolidation, bulk status/priority/agent changes). Distinct from single-task update tool.

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?

Describes when to use (consolidation, bulk changes) but lacks explicit when-not-to-use or alternatives. Context from siblings makes it 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/HuntsDesk/ve-vibe-board'

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