MCP Discord Bot Server

discord_edit_message

To edit a Discord message sent by the proxied account, provide the channel ID, message ID, and new content. Only messages from the proxied account are editable.

Instructions

Edit a message previously sent by the proxied Discord account.

Only messages sent by the proxied account can be edited.

Args:
    channel_id: The ID of the channel containing the message.
    message_id: The ID of the message to edit.
    content: The new text content for the message.

Returns:
    JSON object with the updated message details.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	Yes	The new text content for the message. Required.
`channel_id`	Yes	The ID of the Discord channel containing the message. Required.
`message_id`	Yes	The ID of the message to edit. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A4/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. It discloses the ownership restriction and that a JSON result is returned, but says nothing about required permissions/scopes, rate limits, or what happens to embeds/attachments when content is replaced.

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?

Front-loads the action and its key constraint in two short sentences before the boilerplate Args/Returns blocks; nothing is padded or ambiguous.

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?

An output schema exists, so return values need not be explained (the Returns line is redundant but harmless). The description covers purpose, precondition, and params adequately for a simple 3-param mutation, though permission requirements are 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 coverage is 100%, so all three parameters are already documented in the schema. The Args section merely repeats the same descriptions, adding no syntax, format, or ID-source guidance beyond the structured data.

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 (Edit) and resource (a message), plus scope ('previously sent by the proxied Discord account'), which distinguishes it from sending or deleting a message among the siblings.

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?

Gives a clear precondition for use: only messages sent by the proxied account can be edited. It does not name an alternative tool (e.g., delete + send) for messages that can't be edited, but the constraint is explicit.

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

Deploy Server