Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Edit a message

edit_message
Idempotent

Edit a bot-sent Discord message's text or embeds, and optionally hide link previews. Use it to update or correct bot posts; it cannot modify other users' messages.

Instructions

Edits a message the bot sent (content and/or embeds). suppress_embeds hides link previews on any message (needs Manage Messages for others' messages). Bots cannot change other users' text.

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": {
      "message": "<message>"
    },
    "name": "edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoInstead of channel: a user (ID, <@mention> or name) whose DM channel to use.
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
embedsNoUp to 10 rich embeds.
channelNoChannel or thread: ID, <#mention>, link, or name. Archived threads by ID or link.
contentNoNew text. Pass "" to remove the text.
messageYesMessage ID or message link (https://discord.com/channels/...). With a link, channel is optional.
suppress_embedsNoHide (true) or show (false) link embeds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so safety is partly covered; the description adds real value on top by disclosing the permission requirement ('needs Manage Messages for others' messages') and the hard platform limit on editing other users' text. It does not describe failure behavior when the target message is not bot-authored, which keeps it below 5.

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?

Three short sentences with no filler: capability first, then the parameter nuance, then the hard restriction. Each sentence carries distinct information and nothing is repeated from the schema.

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?

With 7 parameters, full schema coverage, and annotations covering the safety profile, the description supplies exactly the missing behavioral context: scope, permissions, and the bot-only restriction. It stops short of explaining what happens on an invalid target or whether an edit with neither content nor embeds is rejected, but those are edge cases rather than core gaps.

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, but the description goes further by clarifying that suppress_embeds applies to 'any message' rather than only bot messages and by noting the permission dependency. It also frames content and embeds as independently optional ('content and/or embeds'), matching the schema's single required message parameter.

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?

States a specific verb and resource ('Edits a message') and immediately constrains the target ('the bot sent'), which separates it from delete_message and send_message by verb alone. It does not explicitly name a sibling to route against, so it falls short of a 5.

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 scope statement ('a message the bot sent') tells the agent when this tool applies, and 'Bots cannot change other users' text' rules out an obvious misuse case. It never points to delete_message or send_message as the alternative when an edit is not appropriate, so guidance is clear but not complete.

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