discord-mcp

Edit a bot message

discord_edit_message

Idempotent

Edits a bot-posted Discord message's text or embed by channel and message ID, enabling in-place updates and preventing edits to other users' messages.

Instructions

Edit a message this bot posted earlier (text and/or embed). Other people's messages can't be edited.

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>"
    },
    "name": "discord_edit_message"
  }
}

Input Schema

Name	Required	Description
`embed`	No	A formatted card (title, description, colour bar, fields)
`content`	No
`channel_id`	Yes	Channel, thread or post ID
`message_id`	Yes	The bot's message

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=true and destructiveHint=false, so the mutation-safety profile is covered. The description usefully adds the ownership constraint and hints that content and embed are independently updatable, but it does not say what happens to fields that are omitted, whether an empty edit clears them, or what permission model applies.

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?

Two short sentences with the ownership constraint front-loaded and zero redundant wording. Nothing could be removed without losing 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 partially-updating edit with no output schema, the definition covers the critical eligibility question (whose messages) and the mutable surface. It leaves a modest gap around partial-update semantics and the shape of the result, which matters because no output schema exists to answer it.

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 description coverage is 75% and most parameters are already documented, including the nested embed card and its length/format constraints. The phrase 'text and/or embed' adds the meaningful signal that both are optional and can be changed independently, but it adds nothing about identifier formats or embed field semantics.

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?

The description gives a specific verb (edit) and resource (a message this bot posted) and narrows the scope to text and/or embed content. It implicitly rules out editing other users' messages, which separates it from an admin message-management tool, but it never names that sibling explicitly.

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?

It states clearly when the tool applies (messages authored by this bot) and gives an explicit exclusion (other people's messages can't be edited). It stops short of pointing the agent to the right alternative when the exclusion applies.

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

Deploy Server