Skip to main content
Glama
grooving6

discord-mcp

by grooving6

Delete message

delete_message

Delete a Discord message by specifying its channel and message ID.

Instructions

Delete a single message by its id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverNoServer (guild) name or id. Optional when the bot is in a single server or DISCORD_GUILD_ID is set.
channelYesChannel the message is in (name or id).
message_idYesId of the message to delete.
Behavior2/5

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

No annotations provided, and the description does not disclose important behaviors like required permissions (e.g., manage_messages), irreversibility, rate limits, or constraints like message age. The agent is left unaware of these critical details.

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?

A single, front-loaded sentence with no unnecessary words. It efficiently conveys the core functionality.

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?

Given no output schema or annotations, the description is too minimal. It omits failure cases, permission dependencies, and important Discord-specific limitations (e.g., cannot delete messages older than 14 days). This incompleteness could lead to errors.

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 descriptions for all parameters, so baseline is 3. The tool description does not add extra meaning beyond the schema, which is acceptable but not improved.

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?

The description clearly states the action (delete), the resource (a single message), and the identification method (by its id). It is specific and distinguishes from sibling tools like delete_channel or delete_emoji.

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?

No information on when to use this tool versus alternatives, such as edit_message or other deletion tools. It lacks context on prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/grooving6/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server