Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_webhook_with_token

Destructive

Permanently removes a Discord webhook by authenticating with its ID and token. Use it to revoke an exposed or unused webhook and optionally record a reason in the audit log.

Instructions

Delete Webhook with Token. [DELETE /webhooks/{webhook_id}/{webhook_token}]

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>",
      "webhook_token": "<webhook_token>"
    },
    "name": "delete_webhook_with_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
webhook_idYesWebhook ID
webhook_tokenYesWebhook token

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the agent knows this is an irreversible-looking external mutation. The description adds the token-based auth route via the endpoint path, but says nothing about side effects, token invalidation, or required permissions beyond what annotations imply.

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

Conciseness4/5

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

The definition is extremely short and front-loaded, with no filler. It is concise, though the brevity leaves much of the behavioral burden to annotations and schema.

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 requiring a secret token, the definition omits when to use it versus delete_webhook, what happens after deletion, and any confirmation or permission expectations. Annotations cover the safety profile, but the description remains too thin for an agent choosing among several deletion siblings.

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 webhook_id, webhook_token, and reason are already documented. The description does not add format, validation, or audit-log behavior details beyond the schema baseline.

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

Purpose4/5

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

The description names a specific verb and resource ('Delete Webhook') and adds a distinguishing qualifier ('with Token'), plus the exact HTTP endpoint. It differentiates this token-authenticated deletion from the sibling delete_webhook only by name, without stating the difference explicitly.

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 guidance on when to choose this over delete_webhook or other deletion siblings, and no prerequisites such as needing a valid webhook token. The only usage signal is the embedded endpoint path.

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