Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_webhook

Destructive

Permanently deletes a Discord webhook by its ID, invalidating its token so existing integrations stop working. Use it to remove unused webhooks; requires Manage Webhooks permission.

Instructions

Permanently delete a webhook by its ID, invalidating its token. IRREVERSIBLE: any integrations using the old token will stop working. Requires the Manage Webhooks permission. To remove one message the webhook sent, use discord_delete_webhook_message instead; discord_list_webhooks finds the 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": "discord_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhook_idYesID (snowflake) of the webhook to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / webhook_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed1 schema field changedv1.6.0
    • addedInput schema / properties / webhook_id / description
      Added value: +"ID (snowflake) of the webhook to delete."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: token invalidation, the downstream breakage of existing integrations, and the Manage Webhooks permission requirement. It does not mention what happens on a repeat call (annotation marks it non-idempotent), which is the one remaining gap.

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

Conciseness5/5

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

Three sentences, each doing distinct work: what it does, the irreversible consequence, then the permission and alternatives. The warning is front-loaded and no wording is wasted.

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

Completeness5/5

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

For a single-parameter destructive mutation with no output schema, the description covers the action, the blast radius, the required permission, and the alternative tools. Nothing an agent needs in order to call it safely is missing.

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 coverage is 100% and the schema already documents webhook_id as a snowflake with a regex pattern. The description only repeats "by its ID" and adds no format, sourcing, or validation meaning beyond what the schema provides, so the baseline 3 applies.

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

Purpose5/5

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

The description opens with a specific verb and resource ("Permanently delete a webhook by its ID") and immediately names the sibling it must not be confused with (discord_delete_webhook_message). An agent can distinguish this from the sibling webhook tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly routes the agent: use discord_delete_webhook_message to remove a single message, and discord_list_webhooks to find the ID. That covers both the when-not condition and the prerequisite step, leaving nothing to inference.

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