Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

reply_to_message

Replies to a specific Discord message using its link or channel and message IDs, with optional text, attachments, embeds, polls, and mention settings.

Instructions

Reply to a specific message (give its link, or channel_id + 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": {
      "message": "<message>"
    },
    "name": "reply_to_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttsNo
pollNoRaw poll object (or use create_poll)
filesNoFiles to attach (each: path, url or data_base64)
embedsNoEmbeds (bots/webhooks only)
silentNo@silent: send without notifications
contentNoMessage text (Markdown; mention users with <@id>, channels with <#id>, roles with <@&id>, custom emoji <:name:id>)
messageYesMessage link, or message ID with channel_id
channel_idNo
componentsNoComponents (bots only)
sticker_idsNoUp to 3 sticker IDs
mention_replyNoPing the author of the replied message (default true)
suppress_embedsNoHide link previews
allowed_mentionsNo{parse:["users","roles","everyone"], users:[], roles:[], replied_user}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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 given. Beyond that the description discloses nothing: it doesn't say the reply posts publicly, that it notifies the original author by default (mention_reply defaults true), or that the tool is unusable in some channel types. For a mutation tool that sends a message, the description adds essentially no behavioral context.

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 tightly written sentence with the core action front-loaded and the targeting detail in a parenthetical. No waste, though it is arguably too terse for a 13-parameter tool.

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 13-parameter, nested-object message-sending tool with no output schema, the definition is thin: it never says that the reply body goes in 'content', that files/embeds/polls are optional enrichments, or how mention_reply and allowed_mentions interact. The rich schema compensates partially, but an agent still has to infer how to actually compose the reply.

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 description coverage is 85%, so the baseline is 3. The description's parenthetical about link vs. channel_id + message_id duplicates what the 'message' parameter description already says, so it adds no meaning beyond the schema and says nothing about the other 12 parameters (content, files, poll, etc.).

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 ("Reply to a specific message") that clearly distinguishes it from send_message or get_message. The parenthetical even explains the two ways to target a message. It stops short of explicitly naming a sibling alternative, which keeps it from 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?

The guidance is implied: it tells you to supply a link or channel_id + message_id, which implicitly says 'use this instead of send_message when you're replying in-thread.' However, there is no explicit when-to-use/when-not, no mention of create_thread_from_message or send_message as alternatives, and no stated preconditions.

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