Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_edit_message

Modify a message your Discord account already sent by providing its channel ID, message ID, and updated content. Use it to correct or update sent messages.

Instructions

Edit a message the account sent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channelId": "<channelId>",
      "messageId": "<messageId>",
      "content": "<content>"
    },
    "name": "discord_edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
channelIdYesDiscord id (snowflake)
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It discloses the ownership precondition, but says nothing about required permissions, whether the content parameter replaces the entire message body, whether embeds/attachments survive, rate limiting, or failure modes for messages that are too old or not owned by the account.

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?

One short sentence with no wasted words, front-loading the action and the key scoping constraint. It is efficient, though its brevity reflects under-specification rather than tightness of a complete explanation.

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?

For a destructive-capable mutation with no annotations, no output schema, and partially documented parameters, the description is too thin. An agent gets no confirmation of replacement semantics, permission requirements, or return behavior, which are exactly the gaps the structured fields leave open.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — just channelId is documented as a snowflake, while messageId is only a $ref and content has only a maxLength. The description adds no meaning to any of the three parameters, notably failing to clarify that content is a full replacement rather than a patch.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Edit a message the account sent" states a specific verb (edit) and resource (message), and adds a scope constraint that it must be the account's own message. That distinguishes it from discord_get_message or discord_send_message even without naming them, though it does not explicitly contrast with siblings like 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 Guidelines2/5

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

There is an implied precondition (only messages the account itself sent can be edited), which is useful. But there is no explicit guidance on when to use this versus alternatives such as deleting and resending, and no statement about what happens when the target message was authored by someone else.

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