Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

delete_message

Destructive

Delete a Discord message by channel and message ID, optionally recording an audit-log reason. Use it to remove your own messages or others' when you have Manage Messages permission.

Instructions

Delete a message (yours, or anyone's with Manage Messages). [DELETE /channels/{channel_id}/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": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds real value beyond that by disclosing the authorization rule (own message, or Manage Messages for others), which is the decisive behavioral fact for this operation.

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?

One front-loaded sentence plus a bracketed REST route; nothing is wasted. The endpoint annotation is compact and helpful for agents mapping to HTTP semantics.

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

Completeness4/5

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

For a three-parameter destructive call whose annotations already declare destructiveness and whose schema is fully described, the description covers action, permission gate, and endpoint. Only minor gaps remain, such as irreversibility or interaction with bulk deletion.

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%, with channel_id and message_id fully described and reason documented as audit-log visible, so the description need not repeat them. It adds only the ownership notion implied by 'yours', matching the baseline for a fully-documented schema.

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 and resource ('Delete a message') and immediately scopes it with the ownership/permission condition. It does not name a sibling such as bulk_delete_messages or delete_webhook_message, but the core action is unambiguous.

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

Usage Guidelines3/5

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

The parenthetical 'yours, or anyone's with Manage Messages' implies when this call will succeed, which is useful context. However, there is no explicit guidance on when to pick this over bulk_delete_messages or when a webhook message deletion route is required, so routing is left 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