@illodev/taiga-mcp

taiga_userstories_list

List Taiga user stories with optional filters like status, assignee, tags, and milestone to find the stories you need.

Instructions

List user stories with optional filters.

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": "taiga_userstories_list"
  }
}

Input Schema

Name	Required	Description
`epic`	No	Epic ID
`role`	No	Role ID
`tags`	No	Comma-separated tags
`status`	No	Status ID
`project`	No	Project ID
`order_by`	No	Order field
`watchers`	No	Watcher user ID
`milestone`	No	Milestone/Sprint ID
`assigned_to`	No	Assigned user ID
`exclude_role`	No
`exclude_tags`	No
`exclude_status`	No
`milestone__isnull`	No	True for backlog stories
`status__is_closed`	No
`exclude_assigned_to`	No
`status__is_archived`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'optional filters' but does not disclose pagination, default limits, response structure, or any side effects, leaving significant behavioral traits unspecified.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the verb, and contains no filler. It is concise and for what it states, it is efficient, though it may be too sparse for full usefulness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters, no annotations, and no output schema, the description is grossly inadequate. It provides no context on how the listing behaves, what fields are returned, how filters combine, or any other essential information for correct invocation.

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

Parameters2/5

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

Schema description coverage is 63%, so the schema carries most of the parameter meaning. The description adds no specific parameter semantics; 'optional filters' is generic and does not help with the undocumented parameters such as exclude_role, exclude_tags, or status__is_closed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists user stories, using a specific verb and resource. It does not explicitly differentiate from sibling list tools for other entities, but the resource name in the tool name itself makes the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as taiga_userstories_get or taiga_userstories_get_by_ref. The description only states what it does, not when to choose it or when to prefer alternatives.

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

Deploy Server