Skip to main content
Glama

discord_reply_dm

Reply to a specific bot message in a Discord DM by providing user ID, message ID, and reply content.

Instructions

Reply to a specific message in a DM conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesThe Discord user ID.
message_idYesThe message ID (must be a bot message).
contentYesThe reply content.

Implementation Reference

  • Handler for discord_reply_dm: fetches the user, creates DM channel, fetches the target message, and replies to it.
    case "discord_reply_dm": {
      const user = await discord.users.fetch(validateId(args.user_id, "user_id"));
      const dm = await user.createDM();
      const msgId = validateId(args.message_id, "message_id");
      const target = await dm.messages.fetch(msgId);
      const sent = await target.reply(args.content as string);
      return { content: [{ type: "text", text: `✅ DM reply sent to ${user.username} (message id: ${sent.id}).` }] };
    }
  • Schema definition for discord_reply_dm: requires user_id, message_id, and content.
    {
      name: "discord_reply_dm",
      description:
        "Reply to a specific message in a DM conversation.",
      inputSchema: {
        type: "object",
        properties: {
          ...userIdProp,
          ...messageIdProp,
          content: { type: "string", description: "The reply content." },
        },
        required: ["user_id", "message_id", "content"],
      },
    },
  • The dm module is imported and registered in the tool registry, making discord_reply_dm available for routing.
    import dm from "./dm.js";
    
    const modules: ToolModule[] = [
      discovery,
      messages,
      channels,
      permissions,
      members,
      roles,
      moderation,
      screening,
      stats,
      forums,
      webhooks,
      scheduledEvents,
      invites,
      dm,
    ];
  • Imports discord client instance and validateId helper used in the handler.
    import { EmbedBuilder, ColorResolvable } from "discord.js";
    import { discord, validateId } from "../client.js";
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It does not mention side effects, permissions, rate limits, or that the reply appends to the DM thread. The schema hints at constraints but the description itself adds no transparency.

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?

The description is a single 8-word sentence, highly concise. However, it could incorporate minimal additional context (e.g., constraints) without becoming verbose.

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 simple 3-param tool with no output schema, a minimal description is acceptable. However, it lacks mention of the prerequisite that the message must be from the bot (implied in schema) and does not clarify if the reply is a threaded reply or a new message in the DM.

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 100%, so the baseline is 3. The description adds no extra meaning beyond the schema's parameter descriptions. The schema already explains each parameter adequately.

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 'Reply to a specific message in a DM conversation' uses a specific verb ('Reply') and resource ('specific message in a DM conversation'), clearly distinguishing it from siblings like discord_send_dm (send new DM) and discord_edit_dm (edit a message).

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 on when to use this tool versus alternatives like discord_send_dm or discord_edit_dm. The schema notes message_id must be a bot message, but this is not mentioned in the description, leaving the agent without contextual selection criteria.

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