Skip to main content
Glama
Oratorian

Discord MCP Server

by Oratorian

Edit Discord Message

discord_edit_message
Idempotent

Edit a previously sent bot message in a Discord channel by specifying the channel ID, message ID, and new content. Overwrites the message text up to 2000 characters.

Instructions

Edit a message sent by the bot.

Args:

  • channel_id (string): Discord channel ID

  • message_id (string): Message ID to edit

  • content (string): New message content (max 2000 characters)

Returns: Confirmation of edit

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesNew message content (max 2000 characters)
channel_idYesDiscord channel ID (snowflake)
message_idYesDiscord message ID (snowflake)
Behavior3/5

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

Annotations indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds no further behavioral details (e.g., whether content is fully replaced or appended). It does not contradict annotations.

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?

The description is brief and well-structured, with a clear single sentence followed by Args and Returns. No unnecessary information, though the Args list is redundant with the schema.

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

Completeness3/5

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

Given no output schema, the Returns line provides minimal confirmation but lacks error handling or prerequisites (e.g., message must be from bot). Adequate for a simple tool but leaves gaps.

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. The description repeats the content max length but adds no new semantics beyond the schema. Baseline 3 is appropriate.

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 'Edit a message sent by the bot', specifying the action and resource. The title confirms the purpose, and it distinguishes from sibling tools like discord_send_message and discord_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 Guidelines3/5

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

The description implies the tool only edits bot-sent messages but does not explicitly state when to use it versus alternatives (e.g., sending a new message or deleting). No direct comparisons or exclusion criteria are provided.

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/Oratorian/discord-node-mcp'

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