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

@illodev/taiga-mcp

by illodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taiga_wiki_links_delete

Delete a wiki link by providing its ID. Removes unwanted wiki connections from your Taiga project.

Instructions

Delete 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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWiki link ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only restates the operation and resource. It does not mention whether deletion is permanent, what side effects occur, or any authorization requirements.

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

Conciseness5/5

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

The description is a single sentence with no wasted words. It is front-loaded and immediately communicates the action and target.

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

Completeness3/5

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

The tool is simple with one parameter and no output schema, so this is minimally adequate. However, it lacks useful context about how to obtain the wiki link ID, whether deletion is irreversible, and how this operation differs from deleting a wiki page.

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?

The input schema fully documents the only parameter 'id' as 'Wiki link ID', so the description does not need to add more. The description adds no extra semantic meaning, but the schema coverage is sufficient.

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 clearly states the action ('Delete') and the resource ('a wiki link'), making the purpose unambiguous. It also differentiates from siblings such as taiga_wiki_delete by targeting wiki links rather than wiki pages.

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 usage guidance is provided. There is no mention of when to use this tool, any prerequisites, or how it compares to alternatives like taiga_wiki_links_update or taiga_wiki_delete.

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