Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_delete_message

Permanently remove a Discord message by channel and message ID after explicit confirmation, making irreversible deletions intentional and verifiable.

Instructions

Permanently delete a message. Requires confirm: true.

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": {
      "channelId": "<channelId>",
      "messageId": "<messageId>",
      "confirm": "<confirm>"
    },
    "name": "discord_delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Deletion cannot be undone.
channelIdYesDiscord id (snowflake)
messageIdYes

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?

With no annotations, the description carries the full burden, and it does disclose the two most important traits: the operation is permanent and gated behind confirm. It omits permission requirements (e.g. MANAGE_MESSAGES), whether other users' messages are deletable, and what happens on failure or unknown messageId, which matters for an irreversible mutation.

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 sentences, front-loaded with the destructive nature and the prerequisite. No filler, though the extreme terseness leaves behavioral questions unanswered rather than being optimally calibrated.

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 an irreversible delete with zero annotation coverage and no output schema, the definition is thin: it gives no permissions model, no scoping (own vs. others' messages, DM vs. guild), and no indication of the response or error surface.

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 67%, so the schema already documents all three parameters, including the const:true constraint and the snowflake pattern for ids. The description's mention of confirm adds nothing beyond that, though the remaining gap is small since ids are self-explanatory.

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?

"Permanently delete a message" gives a specific verb and resource, and the permanence qualifier separates it from soft/hide-style operations. It does not explicitly contrast with adjacent tools like discord_edit_message or discord_pin_message, but the resource itself is unambiguous against the delete_* siblings.

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 guidance: nothing says when deletion is preferable to editing, whether you can delete messages authored by others, or when the tool will fail. The only directive is the mechanical "Requires confirm: true."

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