delete_topic
Permanently removes a topic and all its posts from the forum.
Instructions
Delete a topic (permanent, cascades to posts)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| topicId | Yes | The topic ID |
Permanently removes a topic and all its posts from the forum.
Delete a topic (permanent, cascades to posts)
| Name | Required | Description | Default |
|---|---|---|---|
| topicId | Yes | The topic ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide destructiveHint=true, but the description adds value by clarifying that deletion is permanent and cascades to posts, which is beyond the annotation.
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, front-loaded with the purpose, and contains no unnecessary words.
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?
Given the low complexity and lack of output schema, the description adequately covers the main behavioral aspects (permanence, cascading) but omits prerequisites or return value, though these are not critical for this simple tool.
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?
Schema coverage is 100% (only one parameter), and the description adds no extra meaning beyond what the schema already provides ('The topic ID').
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 verb 'Delete' and the resource 'topic', and adds 'permanent, cascades to posts' to clarify scope and effect, distinguishing it from sibling delete tools.
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?
The description implies use for permanent deletion but does not explicitly specify when to use or avoid this tool versus alternatives like delete_post or other delete tools.
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/webtoolbox/websitetoolbox-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server