Skip to main content
Glama

discord_reply_message

Reply to a specific message in a Discord channel by providing the channel ID, message ID, and reply content.

Instructions

Reply to a specific message in a channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYesThe message ID to reply to.
contentYes

Implementation Reference

  • The handler implementation for the `discord_reply_message` tool, which fetches the target channel and message, then executes a reply action.
    case "discord_reply_message": {
      const channel = await getTextChannel(args.channel_id as string);
      const target = await channel.messages.fetch(args.message_id as string);
      const sent = await target.reply(args.content as string);
      return { content: [{ type: "text", text: `✅ Reply sent (id: ${sent.id}) to message ${args.message_id} in #${channel.name}.` }] };
    }
  • The tool definition and input schema for `discord_reply_message`.
      name: "discord_reply_message",
      description: "Reply to a specific message in a channel.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          message_id: { type: "string", description: "The message ID to reply to." },
          content: { type: "string" },
        },
        required: ["channel_id", "message_id", "content"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Reply to a specific message') but does not mention any behavioral traits, such as required permissions, rate limits, whether the reply is public or private, or how it interacts with Discord's threading or notification systems. This leaves significant gaps in understanding the tool's behavior beyond the basic operation.

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, clear sentence: 'Reply to a specific message in a channel.' It is front-loaded with the core action, has zero wasted words, and is appropriately sized for the tool's complexity, making it highly efficient and 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?

Given the complexity of a Discord messaging tool with 3 parameters, no annotations, no output schema, and low schema description coverage (33%), the description is incomplete. It lacks details on behavioral aspects (e.g., permissions, effects), parameter usage, and output expectations, leaving the agent with insufficient context to use the tool effectively beyond the basic action stated.

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 33% (only 'message_id' has a description), so the description must compensate for low coverage. However, the description does not add any parameter semantics beyond what is implied by the tool name and action. It mentions 'a specific message' and 'in a channel', which loosely map to 'message_id' and 'channel_id', but provides no details on format, constraints, or the purpose of 'content'. This aligns with the baseline expectation given the schema's partial documentation.

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?

The description clearly states the tool's purpose: 'Reply to a specific message in a channel.' It specifies the verb ('Reply to') and resource ('a specific message in a channel'), making the action explicit. However, it does not distinguish this tool from its sibling 'discord_send_message', which might be used for similar purposes but without replying to a specific message, leaving some 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?

The description provides no guidance on when to use this tool versus alternatives, such as 'discord_send_message' for sending messages without replying or 'discord_edit_message' for modifying existing messages. It lacks explicit context, prerequisites, or exclusions, offering minimal usage direction beyond the basic action stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PaSympa/discord-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server