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

@illodev/taiga-mcp

by illodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taiga_wiki_links_update

Update an existing wiki link in Taiga by specifying its ID, with options to change href, order, or title.

Instructions

Update 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": {
      "id": "<id>"
    },
    "name": "taiga_wiki_links_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWiki link ID
hrefNo
orderNo
titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 of behavioral disclosure, but only states the verb 'update.' It does not explain whether the update is partial or full replacement, whether permissions are required, or what happens if the link does not exist.

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

Conciseness3/5

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

The description is a single, concise sentence with no wasted words, but it is under-specified. While brevity is good, the lack of any additional structure or detail makes it nearly a tautology, providing only the action and resource without context.

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?

Given that this is a mutation tool with 4 parameters, no output schema, and no annotations, the description is grossly inadequate. It fails to explain updatable fields, side effects, or response behavior, making it impossible for the agent to know what a successful invocation entails.

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?

The schema has only 25% description coverage (only 'id' is described). The description 'Update a wiki link.' adds no explanation of the href, order, or title parameters, so the agent cannot determine their meaning, optionality, or allowed values.

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 'Update a wiki link.' uses a specific verb ('update') and resource ('wiki link'), clearly identifying the tool's purpose. It also implicitly distinguishes from sibling tools like taiga_wiki_update (updates a wiki page) and taiga_wiki_links_create/get/delete by focusing on the update action for wiki links.

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 taiga_wiki_links_create, taiga_wiki_links_delete, or taiga_wiki_update, and offers no context about prerequisites or scenarios where partial updates are needed.

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