mcp-discord-bridge

edit_message

Update a bot message using its channel and message IDs. Replace the content with new text up to 2000 characters.

Instructions

Edit a bot message by channel and message ID

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": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>",
      "content": "<content>"
    },
    "name": "edit_message"
  }
}

Input Schema

Name	Required	Description
`channel_id`	Yes
`message_id`	Yes
`content`	Yes	New message content (max 2000 chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 25, 2026

TDQS

B3/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden. It states 'edit' but does not disclose behavioral traits like permissions required, whether it only works on bot messages (implied but not explicit), or any side effects. This is insufficient for a mutation tool.

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?

The description is a single sentence with no superfluous words. It is concise and front-loaded with the core action.

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 the tool's simplicity, the description covers the essentials (edit a bot message by IDs). However, it lacks context about return values (no output schema) and assumes the agent knows this tool is for bot messages only. It is adequate but could be more complete.

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

Parameters1/5

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

The input schema has low description coverage (33%), with only 'content' having a description. The tool description adds no additional meaning beyond the schema, leaving 'channel_id' and 'message_id' without any context.

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 (edit), the resource (bot message), and the identifiers (channel and message ID). It is specific and distinguishes from sibling tools like delete_message or send_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?

No guidance is provided on when to use this tool versus alternatives, such as when to edit a user message vs a bot message. There is no mention of exclusions or prerequisites.

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