Skip to main content
Glama
drvova

Discord MCP Server

discord_add_reaction

Add emoji reactions to Discord messages by specifying channel, message ID, and emoji. This tool enables interactive message responses within Discord servers.

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

  • The core handler function that executes the discord_add_reaction tool logic. Validates input parameters using AddReactionSchema and delegates the actual Discord API call to DiscordService.addReaction.
    async addReaction(channelId: string, messageId: string, emoji: string): Promise<string> {
      const parsed = schemas.AddReactionSchema.parse({ channelId, messageId, emoji });
      return await this.discordService.addReaction(parsed.channelId, parsed.messageId, parsed.emoji);
    }
  • Zod schema defining the input parameters and validation for the discord_add_reaction tool: channelId, messageId, and emoji.
    export const AddReactionSchema = z.object({
      channelId: z.string().describe("Discord channel ID"),
      messageId: z.string().describe("Discord message ID"),
      emoji: z.string().describe("Emoji (Unicode or string)")
    });
  • Dynamic registration/dispatch mechanism in DiscordController that maps tool names like 'add_reaction' (or 'discord_add_reaction') to camelCase method names (e.g., 'addReaction') on AutomationManager for execution.
    private async callAutomationMethod(action: string, params: any): Promise<string> {
      // Convert action name to method name (snake_case to camelCase)
      const methodName = action.replace(/_([a-z])/g, (g) => g[1].toUpperCase());
      
      // Check if method exists
      if (typeof (this.automationManager as any)[methodName] === 'function') {
        // Call the method with params
        return await (this.automationManager as any)[methodName](...Object.values(params));
      }
      
      throw new Error(`Method '${methodName}' not found in AutomationManager`);
    }
  • Helper method in AutomationManager for dynamic execution of actions, supporting snake_case tool names converted to camelCase methods.
    async executeAction(action: string, params: any): Promise<string> {
      // Convert action name to method name (snake_case to camelCase)
      const methodName = action.replace(/_([a-z])/g, (g) => g[1].toUpperCase());
      
      // Check if method exists
      if (typeof (this as any)[methodName] === 'function') {
        // Call the method with params
        return await (this as any)[methodName](...Object.values(params));
      }
      
      throw new Error(`Method '${methodName}' not found in AutomationManager`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Add a reaction' implies a write/mutation operation, it doesn't specify required permissions, rate limits, whether reactions are reversible, or what happens on success/failure. This leaves significant behavioral gaps for a mutation tool.

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 that states the core functionality without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information.

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 insufficient. It doesn't explain what happens after execution (success indicators, error conditions), nor does it provide context about permissions or limitations. The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral context.

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%, with all three parameters clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema, so it meets the baseline for adequate coverage without adding value.

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 the target ('to a message'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'discord_remove_reaction', which performs the opposite action on the same resource type.

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. It doesn't mention prerequisites (like needing appropriate permissions), nor does it differentiate from related tools like 'discord_remove_reaction' or 'discord_edit_message' (which might also modify message appearance).

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

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