Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by qungtai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_delete_message

DestructiveIdempotent

Permanently delete one Discord message by channel and message ID, with optional audit reason and approval before the destructive action.

Instructions

Permanently delete a single message from a channel or thread. To delete between 2 and 100 recent messages at once use discord_bulk_delete_messages. Returns a confirmation object with the deleted message and channel IDs. Bot permissions it may need: View Channel, Manage Messages. Destructive: the user is asked to approve the exact change before it runs.

Input Schema

NameRequiredDescriptionDefault
reasonNoAudit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)
channel_idYesID of the channel or thread that holds the message
message_idYesID of the message

Output Schema

NameRequiredDescriptionDefault
deletedYes
channel_idYesDiscord snowflake ID as a numeric string
message_idYesDiscord snowflake ID as a numeric string

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / channel_id / description
      Added value: +"ID of the channel or thread that holds the message"
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the message"
    • changedInput schema / properties / reason / description
      Previous value: -"Audit log reason"New value: +"Audit log reason sent in the X-Audit-Log-Reason header (up to 512 characters)"
    • addedOutput schema / properties / channel_id / description
      Added value: +"Discord snowflake ID as a numeric string"
    • addedOutput schema / properties / message_id / description
      Added value: +"Discord snowflake ID as a numeric string"
  2. First observedv0.1.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 readOnlyHint=false, yet the description still adds real context: the deletion is permanent, the bot needs View Channel and Manage Messages, and the user is prompted to approve the exact change. It also summarizes the response shape. It does not address what happens on a retry of an already-deleted message, which matters given idempotentHint=true.

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?

Four short sentences, front-loaded with the operation and immediately followed by the sibling routing. The permission and approval notes are useful but the response-format sentence is somewhat redundant against the existing output schema.

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 destructive single-target mutation with an output schema, the definition covers scope, alternatives, permissions, and approval flow, so an agent has what it needs to call safely. Only the retry/already-deleted behavior is unaddressed.

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% and all three parameters (including the audit-log reason header) are documented inline, so the description adds no parameter-level meaning. Baseline 3 applies when the schema does the work.

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 and resource ('Permanently delete a single message') and narrows scope to 'a channel or thread', plus it names the sibling tool it is not (discord_bulk_delete_messages). An agent can distinguish it from the bulk and edit/pin siblings without opening a 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?

Gives an explicit routing rule with a numeric boundary: use bulk delete for 2-100 recent messages, otherwise this tool. It also names the required bot permissions, which is a prerequisite the agent needs before calling.

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