Skip to main content
Glama
Sign In
@illodev/taiga-mcp

@illodev/taiga-mcp

by illodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taiga_task_statuses_bulk_update_order

Bulk reorder task statuses for a project by submitting status ID and order pairs.

Instructions

Bulk update order of task statuses.

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": {
      "project": "<project>",
      "bulk_orders": "<bulk_orders>"
    },
    "name": "taiga_task_statuses_bulk_update_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYesProject ID
bulk_ordersYesArray of [id, order] pairs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It only indicates a write operation ('update order') but does not disclose side effects, permission requirements, expected response format, or whether the operation replaces the entire ordering.

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 concise sentence that is front-loaded with the core action and resource. It earns its place but is perhaps too terse, providing no extra context.

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

Completeness2/5

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

The description is minimal and lacks behavioral context, usage guidance, or return value information. Since there is no output schema and no annotations, the description should provide more context, but it does not explain ordering semantics or prerequisites.

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 both parameters (project ID and bulk_orders as array of [id, order] pairs). The description adds no additional parameter semantics beyond what the schema provides.

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 'Bulk update order of task statuses' clearly states the action (bulk update order), the resource (task statuses), and distinguishes it from sibling tools like taiga_task_statuses_update or other bulk_update_order tools for different resource types.

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 is provided on when to use this tool versus alternatives. It does not mention that this should be used for reordering multiple statuses at once or contrast it with single status updates or other bulk order tools.

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