Skip to main content
Glama
Sign In
backlog-mcp

backlog-mcp

by corbym
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

list_stories

Destructive

List stories from your project backlog, filtered by epic, status, or story type.

Instructions

List stories from the project index, optionally filtered by epic, status, or type. Returns an array of {story_id, title, status, epic_id, story_type} objects. With no filters, returns all stories across all epics. Other tools in this server: get_story, get_index_summary, create_epic, create_story, set_story_status, set_epic_status, add_story_note, set_acceptance_criteria, check_acceptance_criterion, complete_story, bulk_update_stories, bulk_update_epics, bulk_update_acceptance_criteria, groom_epic, reorder_backlog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOptional status to filter by. Valid values: draft, in-progress, done, blocked. When provided, only stories with this status are returned.
epic_idNoOptional epic ID to filter by (e.g. EPIC-003). When provided, only stories belonging to this epic are returned.
story_typeNoOptional story type to filter by. Valid values: feature, bug, chore, spike. When provided, only stories of this type are returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.0
    • changedInput schema / properties / epic_id / description
      Previous value: -"Optional epic ID to filter by, e.g. EPIC-003"New value: +"Optional epic ID to filter by (e.g. EPIC-003). When provided, only stories belonging to this epic are returned."
    • changedInput schema / properties / status / description
      Previous value: -"Optional status to filter by, e.g. draft, in-progress, done"New value: +"Optional status to filter by. Valid values: draft, in-progress, done, blocked. When provided, only stories with this status are returned."
    • addedInput schema / properties / story_type
      Added value: +{
+  "description": "Optional story type to filter by. Valid values: feature, bug, chore, spike. When provided, only stories of this type are returned.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior1/5

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

The description describes a read operation (list stories), but annotations mark destructiveHint=true, suggesting potential mutation. This contradiction is critical and not addressed.

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 a single sentence with a clear structure, front-loading purpose and adding return format and sibling tools efficiently.

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 specifies the return format and covers all necessary information for a filtering list tool.

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?

The description adds default behavior context (returns all stories when no filters) beyond the schema, which already covers parameters well (100% coverage).

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 lists stories from the project index with optional filters, and distinguishes from siblings like get_story and get_index_summary.

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 indicates when to use (listing stories, with or without filters) but does not explicitly exclude alternative tools or provide guidance on when not to use.

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