Skip to main content
Glama
wowjinxy
by wowjinxy

remove_reaction

Remove a bot's reaction from a Discord message by specifying channel, message ID, and emoji to manage message interactions.

Instructions

Remove the bot's reaction from a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
emojiYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function that implements the remove_reaction tool logic. Fetches the Discord channel and message, removes the specified reaction added by the bot, and returns a confirmation message.
    @staticmethod
    async def handle_remove_reaction(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Remove a reaction from a message"""
        channel = await discord_client.fetch_channel(int(arguments["channel_id"]))
        message = await channel.fetch_message(int(arguments["message_id"]))
        
        emoji = arguments["emoji"]
        await message.remove_reaction(emoji, discord_client.user)
        
        return [TextContent(
            type="text",
            text=f"Removed reaction {emoji} from message in #{channel.name}"
        )]
  • Input schema definition for the remove_reaction tool, specifying required parameters: channel_id, message_id, and emoji with their types and descriptions.
    inputSchema={
        "type": "object",
        "properties": {
            "channel_id": {
                "type": "string",
                "description": "Channel containing the message"
            },
            "message_id": {
                "type": "string",
                "description": "Message to remove reaction from"
            },
            "emoji": {
                "type": "string",
                "description": "Emoji to remove (Unicode or custom emoji ID)"
            }
        },
        "required": ["channel_id", "message_id", "emoji"]
    }
  • Registration and dispatch logic for core tools including remove_reaction. Checks if the tool name is in core_tool_names and dynamically calls the corresponding handler method on CoreToolHandlers.
    core_tool_names = [
        "get_server_info", "list_servers", "get_channels", "list_members",
        "get_user_info", "send_message", "read_messages", "add_reaction",
        "add_multiple_reactions", "remove_reaction", "moderate_message",
        "create_text_channel", "delete_channel", "add_role", "remove_role"
    ]
    
    if name in core_tool_names:
        handler_method = f"handle_{name}"
        if hasattr(CoreToolHandlers, handler_method):
            return await getattr(CoreToolHandlers, handler_method)(discord_client, arguments)
  • Tool object creation for remove_reaction, defining name, description, and input schema for MCP registration.
    Tool(
        name="remove_reaction",
        description="Remove a reaction from a message",
        inputSchema={
            "type": "object",
            "properties": {
                "channel_id": {
                    "type": "string",
                    "description": "Channel containing the message"
                },
                "message_id": {
                    "type": "string",
                    "description": "Message to remove reaction from"
                },
                "emoji": {
                    "type": "string",
                    "description": "Emoji to remove (Unicode or custom emoji 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 for behavioral disclosure. While 'remove' implies a mutation, the description doesn't specify permissions required, whether the operation is reversible, rate limits, or error conditions. It mentions 'the bot's reaction' which clarifies scope but doesn't address behavioral traits like what happens if the reaction doesn't exist.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple tool and front-loads the core action and target immediately.

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 3 undocumented parameters, no annotations, and a mutation tool that likely requires specific permissions, the description is incomplete. While an output schema exists (which reduces need to describe return values), the description doesn't address critical context like authentication requirements, error handling, or parameter usage. For a tool that modifies data, this leaves significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description mentions 'message' and 'reaction' but doesn't explain the three required parameters (channel_id, message_id, emoji) or their semantics. It provides no guidance on parameter formats, what constitutes valid emoji, or how to identify channels/messages.

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') and target ('the bot's reaction from a message'), making the purpose immediately understandable. It specifies 'the bot's reaction' which distinguishes it from tools like 'remove_role' that affect different resources. However, it doesn't explicitly differentiate from sibling tools like 'add_reaction' or 'add_multiple_reactions' beyond the verb difference.

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 (e.g., the bot must have previously added the reaction), nor does it contrast with related tools like 'add_reaction' or 'moderate_message'. The agent must infer usage context from the tool name alone.

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

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