Skip to main content
Glama
grooving6

discord-mcp

by grooving6

Edit message

edit_message

Edit previously sent bot messages by providing the channel, message ID, and new content to update the message text.

Instructions

Edit the content of a message the bot sent. The bot can only edit its own messages.

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).
contentYesNew message content.
message_idYesId of the message to edit.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that only the bot's own messages can be edited, which is a key behavioral trait. However, it doesn't mention whether edits are destructive (overwrites previous content) or other side effects like rate limits.

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 sentence of 18 words that is direct and efficient. Every word earns its place, no extraneous information.

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 simple mutation tool with no output schema and no annotations, the description is nearly complete. It specifies the action and constraint. It could mention that the new content replaces old content, but overall it is adequate.

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 4 parameters. The description does not add semantic value beyond stating the tool edits content, which aligns with the 'content' parameter. Baseline score of 3 is appropriate as description adds no extra meaning.

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 verb ('edit') and resource ('content of a message') and includes a critical constraint ('bot can only edit its own messages'), which distinguishes it from siblings like send_message or delete_message.

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

Usage Guidelines4/5

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

The description explicitly states when to use the tool (edit a bot's message) and implicitly when not to (cannot edit others' messages). It does not name alternative tools for similar actions like deleting or sending, but the constraint is clear.

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