@illodev/taiga-mcp

taiga_tasks_create

Create a new task in Taiga by providing project ID and subject, with optional fields for description, assignee, status, and tags. Enables adding tasks directly to Taiga from your AI agent.

Instructions

Create a new task.

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>",
      "subject": "<subject>"
    },
    "name": "taiga_tasks_create"
  }
}

Input Schema

Name	Required	Description
`tags`	No
`status`	No
`project`	Yes	Project ID
`subject`	Yes	Task subject
`watchers`	No
`is_closed`	No
`milestone`	No
`is_blocked`	No
`is_iocaine`	No
`user_story`	No	User Story ID
`assigned_to`	No
`description`	No
`blocked_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.5/5.0

Behavior1/5

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

No annotations are present, so the description must carry the full burden of disclosure. It only states the action 'create' without revealing any side effects, permission requirements, or behavior on invalid input. This adds no information beyond what the tool name already implies.

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, 'Create a new task,' which is concise and front-loaded with the primary action. There is no wasted wording, but it lacks supporting context. It earns a high score for conciseness, though it's not as informative as the calibration example.

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?

For a create operation with 13 parameters and no output schema or annotations, the description is far from complete. It doesn't mention what happens upon success, how the created task is identified, or what the required fields (project, subject) mean beyond the schema. The agent lacks critical context for correct invocation.

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

Parameters1/5

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

With 13 parameters and only 23% schema description coverage, the description offers no additional parameter semantics. The input schema has some descriptions for project, subject, and user_story, but the description does not compensate for the many undocumented fields like tags, status, watchers, is_closed, etc.

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 'Create a new task' uses a specific verb and resource, clearly distinguishing it from sibling create tools for epics, user stories, and issues. The name taiga_tasks_create reinforces the task resource, making 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?

The description provides no guidance on when to use this tool versus alternatives like taiga_userstories_create or taiga_issues_create. It does not mention prerequisites such as the project existing, nor does it specify any conditions or exclusions for use.

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

Deploy Server