Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_webhook_message

Destructive

Permanently deletes a message sent through a webhook using the webhook ID, token, and message ID; no bot permission is needed because the token authorizes this irreversible call.

Instructions

Permanently delete a message that was sent through a webhook, using the webhook's ID and token. IRREVERSIBLE. No bot permission is needed: the token authorizes the call. To delete the webhook itself, use discord_delete_webhook.

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>",
      "message_id": "<message_id>"
    },
    "name": "discord_delete_webhook_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesID of the webhook message to delete.
webhook_idYesID (snowflake) of the webhook that sent the message.
webhook_tokenYesSecret token of the webhook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / webhook_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the webhook message to delete."
    • addedInput schema / properties / webhook_id / description
      Added value: +"ID (snowflake) of the webhook that sent the message."
    • addedInput schema / properties / webhook_token / description
      Added value: +"Secret token of the webhook."
  4. Addedv1.5.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and irreversible semantics, but the description adds meaningful context beyond them: the call needs no bot permission because the webhook token itself authorizes it, and that token is a secret credential. It stops short of describing failure modes (expired/invalid token, message already deleted), which would round it out.

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 short sentences, front-loaded with the operation, then the irreversibility warning, then the auth note and the sibling redirect. No filler or repetition of the schema.

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 three-parameter mutation with full schema coverage, rich annotations, and no output schema, the description covers what the tool does, its danger, its auth model, and its closest alternative. Nothing an agent needs 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 each of the three parameters is documented, so the baseline applies. The description adds only marginal meaning beyond the schema — that the token is the authorization mechanism — which is useful but does not explain formats or constraints the schema lacks.

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?

States a specific verb+resource+scope: 'delete a message sent through a webhook' using webhook ID and token. This distinguishes it from discord_delete_message (regular messages) and discord_delete_webhook (the webhook itself) without requiring the agent to open 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 Guidelines4/5

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

Explicitly routes the agent away from the sibling discord_delete_webhook: 'To delete the webhook itself, use discord_delete_webhook.' The webhook-message framing implicitly excludes regular channel messages, but the description never names discord_delete_message as the alternative for those, leaving one edge case 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