Skip to main content
Glama
Sign In
backlog-mcp

backlog-mcp

by corbym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

bulk_update_acceptance_criteria

Destructive

Set the checked status of specific acceptance criteria on a story. Criteria are matched exactly; all others unchanged. Errors if a criterion is missing.

Instructions

Update the checked state of individual acceptance criteria on a story in one operation. Only the criteria explicitly listed are modified; all others are left untouched. Criteria are matched by exact text. If any criterion text is not found, no changes are made and an error is returned. Returns {story_id, path, criteria_updated, errors}. Call get_story separately if you need to see the resulting content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "story_id": "<story_id>",
      "criteria": "<criteria>"
    },
    "name": "bulk_update_acceptance_criteria"
  }
}

Input Schema

NameRequiredDescriptionDefault
criteriaYesMap of criterion text to desired checked state. true = checked [x], false = unchecked [ ]. Criterion text must match exactly.
story_idYesStory ID to update, e.g. STORY-047

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Discloses partial update behavior, exact match, atomicity (no changes on mismatch), and return shape. Annotations already indicate mutability and destructiveness, but description adds context beyond that.

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?

Four sentences, each with distinct information. Front-loaded with main action. No 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?

Adequately covers all aspects given no output schema. Return format specified. Could add more on success behavior but sufficient.

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 description explains exact matching, boolean meaning, and partial update semantics. Adds value 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?

Clear verb+resource: 'Update the checked state of individual acceptance criteria on a story'. Distinguishes from siblings like check_acceptance_criterion (single) and set_acceptance_criteria (setting list).

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?

Tells when to use (bulk update) and behavior: only listed criteria modified, exact match required, error if not found. Suggests using get_story to see results. Lacks explicit sibling differentiation but context permits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools