@illodev/taiga-mcp

taiga_wiki_links_create

Add a wiki page link to a Taiga project by providing the project ID, link title, and target page slug. Create structured navigation between wiki pages directly through the API.

Instructions

Create a wiki link.

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>",
      "title": "<title>",
      "href": "<href>"
    },
    "name": "taiga_wiki_links_create"
  }
}

Input Schema

Name	Required	Description
`href`	Yes	Wiki page slug to link to
`order`	No
`title`	Yes	Link title
`project`	Yes	Project ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure, but 'Create a wiki link.' only states the basic action. It does not describe side effects, required permissions, response format, or any constraints, providing minimal behavioral context.

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 short sentence with zero wasted words, making it very concise and front-loaded. While it is terse, it earns its place given the tool's simplicity, though it could include a bit more context without losing conciseness.

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?

For a create operation with no annotations and no output schema, this description is incomplete. It lacks context about what a wiki link is, the relationship to wiki pages, or any usage details. The schema covers parameters well, but the overall tool context is missing.

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 coverage is high (75%: project, title, href have descriptions), so the baseline is 3. The description adds no parameter details beyond the schema, but the schema itself already documents most parameter meanings.

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 'Create a wiki link.' has a specific verb and resource, clearly distinguishing it from sibling tools like taiga_wiki_create (create wiki page) and wiki link list/get/update/delete. However, it does not elaborate on what a wiki link is or its purpose, so it's clear but minimal.

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. It does not mention situations where creating a wiki link is appropriate, nor does it reference sibling tools or prerequisites.

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

Deploy Server