Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_webhook

Destructive

Delete a Discord webhook by ID, optionally recording a reason in the audit log.

Instructions

Delete Webhook. [DELETE /webhooks/{webhook_id}]

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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
webhook_idYesWebhook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the HTTP endpoint: it does not say the deletion is permanent, whether the bot must own the webhook, or that the optional reason is recorded in the audit log (that only appears in the schema).

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

Conciseness3/5

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

It is short and front-loaded with no filler, but that is largely because it contains almost no information; the second clause merely restates the REST route rather than explaining behavior.

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

Completeness2/5

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

For a destructive mutation with no output schema, the definition leaves key questions open: permanence of deletion, required auth (bot token vs. webhook token), and how it differs from delete_webhook_with_token. Annotations cover the danger flag but not the operational context an agent needs.

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?

Schema description coverage is 100%, so both webhook_id and the audit-log reason parameter are already documented in the schema. The description adds no syntax, format, or behavioral meaning beyond that, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Delete Webhook" restates the tool name with no elaboration; the bracketed HTTP route confirms the resource but adds nothing an agent could not infer. It does not distinguish this tool from the close sibling delete_webhook_with_token, which likely deletes the same resource via a different auth path.

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?

There is no when-to-use guidance, no exclusions, and no mention of when the token-based alternative or delete_webhook_message should be preferred. The agent must infer selection purely from sibling names.

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