Skip to main content
Glama

discord_add_reaction

Add emoji reactions to Discord messages using channel ID, message ID, and emoji parameters to express responses or engagement.

Instructions

Add a reaction emoji to a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
emojiYesUnicode emoji (e.g. '👍') or custom emoji in format 'name:id'.

Implementation Reference

  • Handler for discord_add_reaction which fetches the message from the channel and adds the specified emoji reaction.
    case "discord_add_reaction": {
      const channel = await getTextChannel(args.channel_id as string);
      const msg = await channel.messages.fetch(args.message_id as string);
      await msg.react(args.emoji as string);
      return { content: [{ type: "text", text: `✅ Reacted with ${args.emoji} to message ${msg.id} in #${channel.name}.` }] };
    }
  • Schema definition for discord_add_reaction tool.
      name: "discord_add_reaction",
      description: "Add a reaction emoji to a message.",
      inputSchema: {
        type: "object",
        properties: {
          channel_id: { type: "string" },
          message_id: { type: "string" },
          emoji: { type: "string", description: "Unicode emoji (e.g. '👍') or custom emoji in format 'name:id'." },
        },
        required: ["channel_id", "message_id", "emoji"],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions adding a reaction but doesn't disclose behavioral traits like whether it requires specific permissions, if there are rate limits, if reactions are reversible, or what happens on success/failure. This is a mutation tool with no safety or operational context.

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 with no wasted words. It's front-loaded with the core action and target, making it easy to parse quickly.

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 this is a mutation tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover permissions, side effects, error conditions, or return values, leaving significant gaps for an AI agent to use it correctly.

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 low (33%), with only the 'emoji' parameter documented. The description doesn't add parameter details beyond the schema, but since there are only 3 parameters and the tool's purpose is straightforward, the minimal description is somewhat adequate. It implies channel_id and message_id are needed to locate the message, which is reasonable.

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 action ('add') and target ('reaction emoji to a message'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like discord_edit_message or discord_reply_message, which also interact with messages, but the specific reaction-focused purpose is clear.

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 is provided on when to use this tool versus alternatives. For example, it doesn't mention whether this is for quick feedback versus editing messages or other message interactions. The description only states what it does, not when it's appropriate.

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