Skip to main content
Glama
drvova

Discord MCP Server

discord_remove_reaction

Remove a specific emoji reaction from a Discord message in a channel. Specify the channel, message, emoji, and optionally the user to manage reactions effectively.

Instructions

Remove a reaction from a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelIdYesThe Discord channel ID
messageIdYesThe message ID to remove reaction from
emojiYesEmoji to remove (Unicode or custom emoji format)
userIdNoUser ID to remove reaction from (defaults to self)

Implementation Reference

  • The core handler function for the discord_remove_reaction tool. It validates input parameters using RemoveReactionSchema and delegates the actual Discord API call to DiscordService.removeReaction.
    async removeReaction(channelId: string, messageId: string, emoji: string): Promise<string> {
      const parsed = schemas.RemoveReactionSchema.parse({ channelId, messageId, emoji });
      return await this.discordService.removeReaction(parsed.channelId, parsed.messageId, parsed.emoji);
  • Zod schema defining the input parameters for the remove reaction tool: channelId, messageId, and emoji.
    export const RemoveReactionSchema = 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. Converts snake_case tool names (e.g., 'discord_remove_reaction' or 'remove_reaction') to camelCase method names on AutomationManager and invokes them. This is how the tool is 'registered' implicitly.
    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`);
    }
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 'Remove' implies a destructive operation, it doesn't specify required permissions, whether the action is reversible, rate limits, or what happens if the reaction doesn't exist. For a mutation tool with zero annotation coverage, this is insufficient.

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 doesn't address behavioral aspects like permissions, side effects, error conditions, or return values. The 100% schema coverage helps with parameters, but overall context for safe/effective use is lacking.

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 all parameters are documented in the schema. The description adds no additional parameter semantics beyond what's already in the schema (like explaining emoji format nuances or userId default behavior). Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Remove a reaction') and target ('from a message'), providing a specific verb+resource combination. It distinguishes from obvious siblings like 'discord_add_reaction' by specifying removal rather than addition, though it doesn't explicitly mention all sibling tools.

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), when not to use it, or how it relates to sibling tools like 'discord_delete_message' or 'discord_edit_message' for message modifications.

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