Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_reply_message

Reply to a specific Discord message using its channel ID, message ID, and content. Attaches a reply reference so clients show it as a threaded reply, and returns the new message ID.

Instructions

Reply to a specific message, attaching a reply reference so clients show it as a threaded reply. Use discord_send_message for a standalone message with no reference. Requires the Send Messages permission. Returns the new reply's 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>",
      "content": "<content>"
    },
    "name": "discord_reply_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesPlain-text body of the reply (max 2000 characters).
channel_idYesID (snowflake) of the channel or thread containing the message.
message_idYesID of the message to reply to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed3 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread containing the message."
    • addedInput schema / properties / content / description
      Added value: +"Plain-text body of the reply (max 2000 characters)."
    • changedInput schema / properties / message_id / description
      Previous value: -"The message ID to reply to."New value: +"ID of the message to reply to."
  4. Addedv1.5.0
  5. Removedv1.0.0
  6. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that a reply reference is attached, that clients render it as a threaded reply, that Send Messages permission is required, and that the response contains the new message ID. No statement contradicts the annotations.

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, each carrying distinct information: behavior, alternative, permission, and return value. It is front-loaded with the core action and contains no filler.

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

Completeness5/5

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

For a simple three-parameter mutation with no output schema, the description covers the essentials: what the tool does, when to use it, what permission is needed, and what it returns. Nothing an agent needs to invoke it correctly is missing.

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 100%, so the schema already documents all three parameters. The description reinforces the relationship between message_id and channel_id by explaining the reply reference, but adds no syntax or parameter-specific detail beyond the schema.

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 opens with a specific verb ('Reply') and a specific resource ('a specific message'), then explains the reply-reference mechanism. It explicitly differentiates itself from discord_send_message, the closest sibling, by contrasting threaded vs standalone messages.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives an explicit routing rule: use discord_send_message for a standalone message with no reference, and by implication use this tool when a reply reference is desired. It also states the required Send Messages permission, giving the agent enough context to decide when to call it.

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