delete_user
Permanently remove a user from the forum by specifying their user ID. Eliminates user account and associated data.
Instructions
Delete a user (permanent)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | The user ID |
Permanently remove a user from the forum by specifying their user ID. Eliminates user account and associated data.
Delete a user (permanent)
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | The user ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
destructiveHint annotation already signals destructive action. Description adds 'permanent', clarifying irreversibility. No additional behavioral context like required permissions 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?
Extremely concise, front-loaded with key action. Could be improved to a full sentence but effectively communicates core purpose without redundancy.
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?
No output schema and description omits return value, success/failure indicators, or side effects. Incomplete for a destructive 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% with 'userId' described. Description adds no extra meaning beyond schema; baseline 3 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?
Description clearly states 'Delete a user (permanent)'. Verb 'Delete' and resource 'user' are specific. Distinguishes from sibling delete tools targeting other resources.
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 guidance on when to use, prerequisites, or alternatives. Agent gets no context about conditions for deletion or comparison to other tools like update_user or create_user.
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