Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_edit_embed

Idempotent

Replace an embed on a bot-sent Discord message with a new embed, using channel and message IDs. Fully overwrites existing embed fields with provided values.

Instructions

Replace the embed on a message previously sent by this bot. Only this bot's messages can be edited. This is a full replace, not a merge: provided fields are applied and omitted fields are dropped from the embed. Returns a confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL that makes the title clickable.
colorNoSide-bar color as a hex string, e.g. '#5865F2'.
titleNoEmbed title shown in bold at the top.
authorNoAuthor block shown at the top of the embed.
fieldsNoUp to 25 name/value field blocks. Set inline:true on a field to render it side-by-side with adjacent inline fields (up to 3 per row).
footerNoFooter text shown at the bottom of the embed.
image_urlNoLarge image shown below the embed body.
timestampNoIf true, stamp the embed with the current time.
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 (an embed is added if it has none).
descriptionNoMain body text of the embed (supports Markdown).
thumbnail_urlNoSmall image shown in the top-right corner.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / author / additionalProperties
      Added value: +false
    • addedInput schema / properties / fields / items / additionalProperties
      Added value: +false
  2. Changed14 schema fields changedv2.0.0
    • addedInput schema / properties / author / properties / icon_url / format
      Added value: +"uri"
    • addedInput schema / properties / author / properties / icon_url / pattern
      Added value: +"^https?://"
    • addedInput schema / properties / author / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / author / properties / url / pattern
      Added value: +"^https?://"
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / color / pattern
      Added value: +"^#[0-9A-Fa-f]{6}$"
    • addedInput schema / properties / image_url / format
      Added value: +"uri"
    • addedInput schema / properties / image_url / pattern
      Added value: +"^https?://"
    • changedInput schema / properties / message_id / description
      Previous value: -"ID of the message to edit. Must be a bot message that already contains an embed."New value: +"ID of the message to edit. Must be a message authored by this bot (an embed is added if it has none)."
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / thumbnail_url / format
      Added value: +"uri"
    • addedInput schema / properties / thumbnail_url / pattern
      Added value: +"^https?://"
    • addedInput schema / properties / url / format
      Added value: +"uri"
    • addedInput schema / properties / url / pattern
      Added value: +"^https?://"
  3. Changed1 schema field changedv1.6.2
    • changedInput schema / properties / fields / description
      Previous value: -"Up to 25 name/value field blocks rendered as a grid."New value: +"Up to 25 name/value field blocks. Set inline:true on a field to render it side-by-side with adjacent inline fields (up to 3 per row)."
  4. Changed17 schema fields changedv1.6.0
    • addedInput schema / properties / author / description
      Added value: +"Author block shown at the top of the embed."
    • addedInput schema / properties / author / properties / icon_url / description
      Added value: +"Small icon shown next to the author name."
    • addedInput schema / properties / author / properties / name / description
      Added value: +"Author display name."
    • addedInput schema / properties / author / properties / url / description
      Added value: +"URL the author name links to."
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread containing the message."
    • changedInput schema / properties / color / description
      Previous value: -"Hex color e.g. #5865F2"New value: +"Side-bar color as a hex string, e.g. '#5865F2'."
    • addedInput schema / properties / description / description
      Added value: +"Main body text of the embed (supports Markdown)."
    • addedInput schema / properties / fields / description
      Added value: +"Up to 25 name/value field blocks rendered as a grid."
    • addedInput schema / properties / fields / items / properties / inline / description
      Added value: +"If true, render this field side-by-side with adjacent inline fields."
    • addedInput schema / properties / fields / items / properties / name / description
      Added value: +"Field heading."
    • addedInput schema / properties / fields / items / properties / value / description
      Added value: +"Field body text."
    • addedInput schema / properties / footer / description
      Added value: +"Footer text shown at the bottom of the embed."
    • addedInput schema / properties / image_url / description
      Added value: +"Large image shown below the embed body."
    • changedInput schema / properties / message_id / description
      Previous value: -"The message ID to edit (must be a bot message with an embed)."New value: +"ID of the message to edit. Must be a bot message that already contains an embed."
    • addedInput schema / properties / thumbnail_url / description
      Added value: +"Small image shown in the top-right corner."
    • changedInput schema / properties / timestamp / description
      Previous value: -"If true, adds the current timestamp to the embed."New value: +"If true, stamp the embed with the current time."
    • addedInput schema / properties / title / description
      Added value: +"Embed title shown in bold at the top."
  5. Addedv1.5.0
  6. Removedv1.0.0
  7. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses the critical behavioral nuance beyond the annotations: this is a full replace, not a merge, so omitted fields are dropped. It also states the bot-only restriction and that a confirmation is returned. The annotations already cover read/write and idempotency, and there is no contradiction.

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 three sentences with no filler: purpose and restriction first, the essential replace-not-merge behavior second, and the return behavior third. Every sentence earns its place.

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?

The schema thoroughly documents all 12 parameters, including nested objects and field limits, and the description covers scope, replacement semantics, and a return confirmation. Since there is no output schema, a slightly richer description of the confirmation payload would make it fully complete, but it is sufficient for correct invocation.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds value by clarifying that omitted optional fields are cleared rather than preserved, which materially affects how an agent should construct arguments. It does not add per-parameter details beyond what the schema already provides.

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 states a specific action and resource: 'Replace the embed on a message previously sent by this bot.' It clearly differentiates this from sending a new embed or editing message text, and the 'Only this bot's messages can be edited' boundary adds precision.

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?

The description provides a clear precondition: the target message must have been sent by this bot, which tells the agent when not to use the tool. However, it does not explicitly name alternatives such as discord_edit_message or discord_edit_dm_embed, so it stops short of full routing guidance.

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