Skip to main content
Glama
wowjinxy
by wowjinxy

add_multiple_reactions

Add multiple emoji reactions to a Discord message in one action using channel ID, message ID, and emoji array inputs.

Instructions

Add multiple reactions to a message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
message_idYes
emojisYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function that executes the add_multiple_reactions tool by fetching the Discord channel and message, then iteratively adding each specified emoji as a reaction, and returning a confirmation message.
    async def handle_add_multiple_reactions(discord_client, arguments: Dict[str, Any]) -> List[TextContent]:
        """Add multiple reactions to a message"""
        channel = await discord_client.fetch_channel(int(arguments["channel_id"]))
        message = await channel.fetch_message(int(arguments["message_id"]))
        
        emojis = arguments["emojis"]
        for emoji in emojis:
            await message.add_reaction(emoji)
        
        return [TextContent(
            type="text",
            text=f"Added {len(emojis)} reactions ({', '.join(emojis)}) to message in #{channel.name}"
        )]
  • Registers the 'add_multiple_reactions' tool in the MCP server's list_tools() function, including the input schema defining required parameters: channel_id, message_id, and emojis array.
    Tool(
        name="add_multiple_reactions",
        description="Add multiple reactions 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"
                },
                "emojis": {
                    "type": "array",
                    "items": {
                        "type": "string",
                        "description": "Emoji to react with (Unicode or custom emoji ID)"
                    },
                    "description": "List of emojis to add as reactions"
                }
            },
            "required": ["channel_id", "message_id", "emojis"]
        }
    ),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't cover critical aspects like required permissions, rate limits, whether reactions are additive or replace existing ones, or error handling. This leaves significant 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 with no wasted words. It's front-loaded with the core action, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 a mutation tool with 3 parameters, 0% schema coverage, no annotations, and sibling tools like 'add_reaction', the description is incomplete. It lacks details on behavior, parameters, and usage context, though the presence of an output schema mitigates some need to explain return values.

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 but fails to do so. It mentions 'multiple reactions' which hints at the 'emojis' array parameter, but doesn't explain what 'channel_id' or 'message_id' refer to, their formats, or constraints on emoji strings. This leaves parameters largely undocumented.

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 verb ('Add') and resource ('multiple reactions to a message'), making the purpose specific and understandable. However, it doesn't explicitly distinguish from its sibling 'add_reaction' beyond implying multiple vs. single reactions, which is a minor gap.

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?

No guidance is provided on when to use this tool versus alternatives like 'add_reaction' or other message-related tools. The description lacks context about prerequisites, permissions, or typical scenarios, leaving the agent with no usage direction.

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