Skip to main content
Glama
Sign In
Discord MCP

Discord MCP

by RestartFU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

edit_message

Destructive

Update an existing Discord message by specifying channel ID, message ID, and new content, when permissions allow.

Instructions

Edit an existing message where the credential permits it.

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

Input Schema

NameRequiredDescriptionDefault
contentYes
channel_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotation destructiveHint=true already signals that this is a mutation. The description adds no extra behavioral detail (e.g., permanent overwrite of content) but does not contradict the annotation either.

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 a single, concise sentence with no unnecessary words. It is front-loaded with the verb and resource, making it easy to parse.

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

Completeness2/5

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

The description omits important context such as the need for the message to exist, the role of channel_id/message_id in locating it, and any potential side effects beyond editing. It relies entirely on the parameter names and annotations.

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

Parameters2/5

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

Schema coverage is 0% (no descriptions for content, channel_id, or message_id). The description does not explain the purpose of these parameters, though their names are somewhat self-explanatory.

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 verb 'Edit' is specific and the resource 'existing message' is clearly defined. It distinguishes from send (creating new) and delete (removing) without ambiguity.

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 guidance is provided on when to use this tool versus alternatives like delete_message or send_message. The phrase 'where the credential permits it' only hints at permission constraints, not usage context.

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