Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

edit_my_message

Update the text content of one of your own Discord messages by using a message link or a message ID plus channel ID.

Instructions

Change the text of one of your messages (message link, or ID + channel_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": {
      "message": "<message>",
      "content": "<content>"
    },
    "name": "edit_my_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
messageYes
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds only that the target must belong to the caller and that it mutates text specifically; it says nothing about edit permissions, whether edits are reversible, or how attachments/embeds are treated.

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?

A single front-loaded sentence with the accepted identifier forms in a compact parenthetical; nothing is redundant. It is arguably too terse for a mutation tool, but there is no wasted wording.

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 3-parameter mutation tool with annotations and no output schema, the core call contract is present: what is changed, on which message, and how to identify it. Gaps remain around permissions, error conditions when the message is not the caller's, and content formatting expectations.

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 0%, so the description must carry the burden — and it does identify the two input forms for 'message' (a link, or an ID paired with channel_id) and clarifies that 'content' is the new text. Only the format of 'content' (markdown vs plain) remains undocumented.

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 ('Change the text of one of your messages') and adds the scope qualifier 'your', which separates it from the sibling edit_message. It does not name an alternative explicitly, so it stops 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 Guidelines3/5

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

Usage is only implied through the possessive 'your messages' — an agent can infer this is the self-scoped edit variant, but there is no explicit statement of when to prefer it over edit_message, nor any prerequisite or exclusion.

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