Skip to main content
Glama
wowjinxy
by wowjinxy

add_reaction

Add emoji reactions to Discord messages by specifying channel, message ID, and emoji. This tool enables interactive responses in Discord conversations through MCP server integration.

Instructions

Add a reaction to a specific message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
emojiYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function that executes the add_reaction tool logic: fetches the channel and message, adds the specified emoji reaction, and returns a confirmation message.
    async def handle_add_reaction(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Add a reaction to 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.add_reaction(emoji)
        
        return [TextContent(
            type="text",
            text=f"Added reaction {emoji} to message in #{channel.name}"
        )]
  • Defines the input schema, parameters, and description for the add_reaction tool in the MCP tool list.
        name="add_reaction",
        description="Add a reaction to a message",
        inputSchema={
            "type": "object",
            "properties": {
                "channel_id": {
                    "type": "string",
                    "description": "Channel containing the message"
                },
                "message_id": {
                    "type": "string",
                    "description": "Message to react to"
                },
                "emoji": {
                    "type": "string",
                    "description": "Emoji to react with (Unicode or custom emoji ID)"
                }
            },
            "required": ["channel_id", "message_id", "emoji"]
        }
    ),
  • Registers and dispatches the add_reaction tool by including it in the core_tool_names list and routing calls to CoreToolHandlers.handle_add_reaction.
    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)
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 operation, it doesn't specify whether this requires specific permissions, what happens if the reaction already exists, rate limits, or what the output contains. The description is minimal and lacks important behavioral 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 extremely concise at just 7 words, front-loading the core functionality with zero wasted words. It efficiently communicates the basic purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that there's an output schema (which handles return values) and the tool has only 3 straightforward parameters, the description covers the basic purpose adequately. However, for a mutation tool with no annotations and 0% schema description coverage, it should provide more context about permissions, constraints, and parameter requirements to be truly complete.

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?

With 0% schema description coverage for all 3 parameters, the description provides no additional semantic information about what 'channel_id', 'message_id', or 'emoji' should contain. It doesn't explain format requirements, constraints, or examples for any of the parameters, failing to compensate for the schema's lack of descriptions.

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 specific message'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'add_multiple_reactions' which serves a similar purpose but with different functionality.

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 like 'add_multiple_reactions' or 'remove_reaction'. It doesn't mention prerequisites, permissions needed, or contextual constraints for adding reactions to messages.

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