Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_webhook_message

Destructive

Delete a specific message from a Discord webhook by providing the webhook ID, token, and message ID. Use it to remove outdated or incorrect webhook messages and optionally log a reason in the audit log.

Instructions

Delete Webhook Message. [DELETE /webhooks/{webhook_id}/{webhook_token}/messages/{message_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>",
      "webhook_token": "<webhook_token>",
      "message_id": "<message_id>"
    },
    "name": "delete_webhook_message"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/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's one added value is the endpoint path, which implies webhook-token authentication rather than bot auth — a meaningful distinction from delete_message. It does not say whether deletion is permanent, what happens on an invalid token, or what the response contains.

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?

Two short, front-loaded sentences with no filler. The bracketed endpoint is arguably mechanical restatement of the name, but it is compact and adds a little routing information rather than bloat.

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

Completeness3/5

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

For a four-parameter destructive tool with full annotation and schema coverage and no output schema, the description is minimally sufficient — an agent can call it correctly. Gaps are the permanence of deletion, error behavior for a bad webhook token, and any statement about the returned payload, which is not covered anywhere else.

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 all four parameters (including the optional audit-log reason) are documented in the schema; baseline is therefore 3. The endpoint template does map webhook_id, webhook_token, and message_id to their URL positions, which is modest added value but nothing beyond that.

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?

States a specific verb+resource ("Delete Webhook Message") and backs it with the exact REST route, so an agent can distinguish it from delete_message and delete_webhook. It stops short of explaining why one would target a webhook message rather than a bot message, which is where ambiguity with siblings remains.

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 or when-not-to-use guidance, no mention of prerequisites, and no explicit pointer to the sibling alternatives (delete_message, bulk_delete_messages). The only implied usage signal is the endpoint path, which the agent must decode itself.

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