Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

edit_message

Update an existing Discord message's text, flags, or attachments and add new files—ideal for correcting content or refreshing attachments without sending a new message.

Instructions

Edit one of your messages (content, flags, attachments to keep). Pass files to add new attachments. [PATCH /channels/{channel_id}/messages/{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>",
      "attachments": "<attachments>"
    },
    "name": "edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoFiles to attach (each: path, url or data_base64)
flagsNo
embedsNo
contentNo
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
componentsNo
message_idYesMessage ID
attachmentsYes
allowed_mentionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation and safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the parenthetical "attachments to keep" reveals that existing attachments are replaced unless re-passed, and the files/attachments split clarifies that new uploads go through a separate parameter. It stops short of permissions, rate limits, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus an endpoint tag: no filler, and the core behavior is front-loaded. The parenthetical field list is slightly compressed, but nothing would be improved by lengthening it materially.

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?

For a 9-parameter mutation with no output schema and a partially documented schema, the description covers the highest-risk semantic (attachment retention) but leaves the agent uninformed about optional rich fields and which parameters are mandatory. Adequate to invoke safely, not complete enough to invoke confidently in one pass.

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 coverage is only 33% across 9 parameters, so the description must compensate and partially does: it distinguishes `files` (add new attachments) from `attachments` (those to keep) and names content and flags. Embeds, components, allowed_mentions, and the fact that `attachments` is required are not addressed, so roughly two-thirds of the surface stays schema-only.

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 ("Edit one of your messages") and enumerates the editable fields, plus the PATCH endpoint for grounding. It does not differentiate itself from close siblings like edit_my_message or edit_webhook_message, so the scope boundary between "one of your messages" and "my message" is left to inference.

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 when-to-use or when-not-to-use guidance is given beyond the implicit "your messages" scoping. With sibling tools such as edit_my_message and edit_webhook_message present, the definition offers no routing signal at all, leaving the agent to guess which edit tool applies.

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