Skip to main content
Glama
hanweg

mcp-discord

by hanweg
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

remove_reaction

Remove specific emoji reactions from Discord messages by specifying the channel, message ID, and emoji. Simplify reaction management on the mcp-discord server.

Instructions

Remove a reaction from a message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYesChannel containing the message
emojiYesEmoji to remove (Unicode or custom emoji ID)
message_idYesMessage to remove reaction from

Implementation Reference

  • src/discord_mcp/server.py:585-592 (handler)
    Handler implementation for the 'remove_reaction' tool. Fetches the specified channel and message, then removes the specified reaction added by the bot user, returning a success confirmation.
    elif name == "remove_reaction":
    channel = await discord_client.fetch_channel(int(arguments["channel_id"]))
    message = await channel.fetch_message(int(arguments["message_id"]))
    await message.remove_reaction(arguments["emoji"], discord_client.user)
    return [TextContent(
        type="text",
        text=f"Removed reaction {arguments['emoji']} from message"
    )]
  • src/discord_mcp/server.py:253-274 (registration)
    Registration of the 'remove_reaction' tool in the list_tools() function, including its name, description, and input schema definition.
    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"]
    }
),

Tool Definition Quality

C2.9/5.0
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 mention required permissions, whether it's destructive, rate limits, or what happens on success/failure. For a mutation tool, this leaves significant gaps in understanding its behavior.

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, clear sentence with zero wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse.

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 lacks information about behavioral traits, error conditions, or what the tool returns, leaving the agent with incomplete context for proper invocation.

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 the schema already documents all three parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema, meeting the baseline for high coverage.

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 ('a reaction from a message'), making the purpose immediately understandable. It doesn't differentiate from siblings like 'add_reaction' or 'add_multiple_reactions' beyond the obvious verb difference, but the purpose is unambiguous.

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 or in what context it should be invoked. The description merely states what it does without indicating prerequisites, constraints, or relationships to sibling tools like 'add_reaction'.

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

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

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