Skip to main content
Glama

bulk_update_stories

Destructive

Update multiple backlog stories at once by setting status, appending notes, or patching acceptance criteria. Errors for missing stories are reported instead of stopping the batch.

Instructions

Update multiple stories in one operation. Each entry may set status, append a note, and/or patch acceptance criteria. Updates are applied atomically per file. If a story does not exist, an error is recorded for that entry and processing continues. Returns an array of per-story result objects with fields: story_id, status_updated, old_status, new_status, note_appended, criteria_updated, criteria_errors, errors.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
updatesYesArray of story update objects. Each must include story_id; status, note, and criteria are optional. status must be one of: draft, in-progress, blocked, deferred (use complete_story to mark done). note is appended, not replaced. criteria is a map of criterion text to boolean checked state.
Behavior4/5

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

Annotations already indicate destructiveHint=true and openWorldHint=true. The description adds that updates are atomic per file, errors for nonexistent stories do not stop processing, and returns per-story results. This aligns with and expands upon the annotations without contradiction.

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 concise—four sentences—with no redundant information. The main purpose is stated first, followed by details on allowed updates, error handling, and return format.

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?

Despite no output schema, the description fully specifies the return format (array of result objects with fields). It covers atomicity, error handling, partial failures, and references to sibling tools. This is comprehensive for a bulk operation.

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 the schema already documents the parameter structure. The description reinforces that notes are appended and status values are restricted, but adds limited new semantic meaning beyond the 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 'Update multiple stories in one operation' and specifies the fields that can be updated. It distinguishes from single-story tools by mentioning complete_story as an alternative for marking done, and the sibling list includes set_story_status, add_story_note, etc.

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 what operations are possible (status, note, criteria) and error handling behavior. It references complete_story for marking done, providing guidance against using this tool for that purpose. However, it does not explicitly state when to use this vs single-update tools or when not to use it.

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/corbym/backlog-mcp'

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