Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_edit_message

Idempotent

Replace the text of a bot-authored Discord message in a channel or thread. Specify channel ID, message ID, and new content; returns the edited message ID.

Instructions

Edit the text content of a message previously sent by this bot. Discord forbids editing other users' messages, so this fails for non-bot messages. Use discord_edit_embed for embed messages. Works in text channels and threads. Returns the edited message ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesNew plain-text content that fully replaces the existing content (max 2000 characters).
channel_idYesID (snowflake) of the channel or thread containing the message.
message_idYesID of the message to edit. Must be a message authored by this bot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread containing the message."
    • changedInput schema / properties / content / description
      Previous value: -"New text content for the message."New value: +"New plain-text content that fully replaces the existing content (max 2000 characters)."
    • changedInput schema / properties / message_id / description
      Previous value: -"The message ID to edit (must be a bot message)."New value: +"ID of the message to edit. Must be a message authored by this bot."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only establish that this is a mutating, idempotent, non-destructive operation; the description goes well beyond them by disclosing the failure mode for non-bot messages, the threading scope, and the return value (edited message ID). Stating the return value is especially valuable given there is no output schema. No contradiction with the annotations.

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?

Four short sentences, each carrying distinct information: core action, failure condition, alternative routing, and scope/return value. The primary purpose is front-loaded and there is zero filler.

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

Completeness5/5

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

For a 3-parameter tool with a fully documented schema, the description fills the gaps that structured data cannot: when it fails, which sibling to use instead, where it works, and what it returns. Nothing needed for correct invocation is missing.

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 100%, with each parameter already documented (snowflake patterns, bot-authorship requirement, max 2000 characters, full replacement semantics). The description adds only marginal reinforcement about channel/thread context, so it stays at the baseline 3 rather than compensating for any gap.

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 and resource: editing the text content of a message previously sent by this bot. It additionally distinguishes itself from its closest sibling by noting 'Use discord_edit_embed for embed messages.' An agent can tell this tool apart without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly names the alternative tool (discord_edit_embed) and the condition that selects it (embed messages), and warns that the operation fails for non-bot messages. It also scopes where the tool works (text channels and threads). This is explicit when/when-not guidance with a named alternative.

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