delete_wiki_page
Permanently delete a wiki page by providing its numeric ID.
Instructions
Delete a wiki page permanently
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wiki_id | Yes | Wiki page numeric ID |
Permanently delete a wiki page by providing its numeric ID.
Delete a wiki page permanently
| Name | Required | Description | Default |
|---|---|---|---|
| wiki_id | Yes | Wiki page numeric ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The word 'permanently' indicates the destructive nature, which adds transparency. However, no annotations are provided, and the description does not disclose other behavioral aspects like error handling, auth requirements, or cascading effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence. It is front-loaded with the action. While it is brief, every word adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool, the description is minimal. It lacks context on error responses, required permissions, or what happens after deletion. More details would be beneficial.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides a clear description of the single parameter (wiki_id as numeric ID). With 100% schema coverage, the tool description does not need to add extra detail; the baseline score is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: permanently deleting a wiki page. The verb 'delete' and the resource 'wiki page' are specific and distinguish it from sibling tools like delete_epic or delete_issue.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidelines are provided about when to use this tool, prerequisites, or alternatives. For a destructive action, information about irreversibility or impact on related entities would be helpful.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/juanleon8581/taiga-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server