Skip to main content
Glama

discord_add_reaction

Add emoji reactions to Discord messages by specifying channel ID, message ID, and emoji. This tool enables users to interact with Discord content through reactions.

Instructions

Add a reaction to a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdYesThe Discord channel ID
messageIdYesThe message ID to react to
emojiYesEmoji to react with (Unicode or custom emoji format)

Implementation Reference

  • Factory function returning the ToolHandler object for 'discord_add_reaction'. Includes input schema validation with Zod, policy check, calls DiscordClient.addReaction, and returns success response. This is the primary implementation of the tool logic.
    export function addReactionTool(dc: DiscordClient, policy: Policy): ToolHandler {
      const input = z.object({ channel_id: z.string(), message_id: z.string(), emoji: z.string() });
      return {
        name: 'discord_add_reaction',
        description: 'Add a reaction emoji to a message.',
        inputSchema: input,
        async *handler({ input }: { input: any }){
          const { channel_id, message_id, emoji } = input as any;
          if (!policy.allowChannel(channel_id)) throw new Error('Channel not allowed by policy');
          await dc.addReaction(channel_id, message_id, emoji);
          yield { content: [{ type: 'text', text: 'ok' }] };
        }
      };
    }
  • DiscordClient helper method that performs the actual Discord REST API call to add a reaction to a message using the bot's own reaction endpoint.
    async addReaction(channelId: string, messageId: string, emoji: string): Promise<void> {
      await this.rest.put(Routes.channelMessageOwnReaction(channelId, messageId, emoji));
    }
  • src/index.ts:153-153 (registration)
    Commented registration of the addReactionTool in the main server setup. Indicates that a generated version is used instead.
    // registerTool(addReactionTool(dc, policy)); // Using generated version instead
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't disclose permissions required, rate limits, whether reactions are reversible, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately understandable without unnecessary elaboration.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., permissions, side effects) and doesn't compensate for the absence of structured fields, leaving significant gaps in understanding how the tool operates.

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 schema fully documents parameters like 'channelId' and 'emoji'. The description adds no additional meaning beyond the action itself, such as explaining emoji formats or ID sources. Baseline 3 is appropriate when schema does all the work.

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 a reaction') and target ('to a message'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'discord_remove_reaction' or 'discord_edit_message', which would require explicit comparison to achieve a perfect score.

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. There are no mentions of prerequisites (e.g., needing message access), exclusions, or comparisons to siblings like 'discord_remove_reaction' or 'discord_send_message', leaving usage context entirely implicit.

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/BennettSchwartz/discord-mcp'

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