@illodev/taiga-mcp

taiga_tasks_bulk_create

Create multiple tasks in Taiga at once by submitting a project ID and newline-separated task subjects. Optionally assign them to a user story, sprint, or status.

Instructions

Bulk create tasks.

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_id": "<project_id>",
      "bulk_tasks": "<bulk_tasks>"
    },
    "name": "taiga_tasks_bulk_create"
  }
}

Input Schema

Name	Required	Description
`us_id`	No	User Story ID
`sprint_id`	No	Sprint/Milestone ID
`status_id`	No
`bulk_tasks`	Yes	Newline-separated task subjects
`project_id`	Yes	Project ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It states that the tool creates tasks in bulk, which is a basic behavior, but it does not explain required fields, the format of bulk_tasks, concurrency/side effects, or the return value. This is minimal disclosure for a mutation tool.

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

Conciseness2/5

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

The description is extremely short, but it is under-specified rather than concisely informative. It is essentially a fragment that repeats the tool name, providing no structural benefit or added context. A good description would be one or two sentences that add value beyond the name.

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?

Given no annotations, no output schema, and five parameters (two required), the description is severely incomplete. It fails to mention that project_id and bulk_tasks are required, how the bulk input is formatted (though schema covers it), what response to expect, or any usage context. This is insufficient for an agent to correctly invoke the tool.

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 80%, so the schema already documents four of five parameters. The description adds no parameter-specific information. It does not clarify the meaning of 'bulk_tasks' beyond what the schema says ('Newline-separated task subjects'), and leaves status_id undocumented. Baseline of 3 applies due to high schema coverage.

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

Purpose3/5

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

The description 'Bulk create tasks.' clearly names the action (create) and resource (tasks), but it adds little beyond the tool name itself. It does not specify what 'bulk' means in practice (e.g., newline-separated subjects) and does not distinguish from the sibling 'taiga_tasks_create' except through the word 'bulk.'

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 such as the single-task create tool. The description does not state prerequisites, typical scenarios, or exclusions. The word 'bulk' implies batch use, but there is no explicit guidance.

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

Deploy Server