delete_webhook
Remove a Discord webhook by providing its ID. Use this tool to clean up or revoke webhooks when no longer needed.
Instructions
Delete a webhook.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| webhook_id | Yes |
Remove a Discord webhook by providing its ID. Use this tool to clean up or revoke webhooks when no longer needed.
Delete a webhook.
| Name | Required | Description | Default |
|---|---|---|---|
| webhook_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only says 'delete', giving no details about irreversibility, authorization needs, or side 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 sentence, front-loaded with the action, but it is under-specified to the point of being unhelpful.
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?
With one required parameter, no output schema, and similar sibling tools, the description lacks essential context such as the effect of deletion and required permissions.
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 description coverage is 0%, and the tool description adds no meaning to the lone parameter 'webhook_id', leaving the agent to guess its format or origin.
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 it deletes a webhook, which is distinct from sibling tools like create_webhook or get_channel_webhooks. However, it could more explicitly mention deletion by webhook ID.
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 this tool vs alternatives, nor prerequisites or consequences of deletion.
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/EncryptMan/discord-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server