Skip to main content
Glama
Yv3s-y4ng

MCP-Discord Stream

by Yv3s-y4ng

discord_remove_reaction

Remove a specific emoji reaction from a Discord message by supplying the channel ID, message ID, and emoji.

Instructions

Removes a specific emoji reaction from a Discord message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiYes
userIdNo
channelIdYes
messageIdYes
Behavior2/5

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

With no annotations, the description carries full behavioral burden, but it only states the action. It does not disclose consequences, such as whether the reaction is removed for the authenticated user or any user, whether it fails silently if no reaction exists, or any permission requirements. The optional userId parameter is left unexplained.

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, front-loaded sentence with no wasted words. It achieves maximum conciseness while conveying the core purpose.

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 the tool's complexity (4 params, no output schema, no annotations, many siblings), the description is far too minimal. It lacks essential context about behavior, parameter roles, and usage scenarios, making it inadequate for an agent to invoke correctly without additional assumptions.

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%, and the description provides minimal parameter insight. It clarifies that 'emoji' refers to the emoji reaction, but channelId, messageId, and userId are not explained. This is insufficient for a 4-parameter tool with no schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Removes') and resource ('specific emoji reaction from a Discord message'), clearly distinguishing it from siblings like discord_add_reaction and discord_add_multiple_reactions. It unequivocally states the primary action and target.

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. It does not specify whether to use it for removing the bot's own reaction or another user's, nor does it mention any prerequisites or conditions. This is a clear gap given the large sibling tool list.

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/Yv3s-y4ng/mcp-discord-stream'

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