Skip to main content
Glama

discord_remove_reactions

DestructiveIdempotent

Remove all reactions from a message, or target specific emoji or user reactions. Requires Manage Messages permission for removing all or another user's reaction.

Instructions

Remove reactions from a message. With no emoji: removes ALL reactions. With emoji only: removes every reaction of that emoji. With emoji and user_id: removes that one user's reaction. Removing all reactions or another user's reaction requires the Manage Messages permission. Use discord_add_reaction to add.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiNoUnicode emoji or custom emoji 'name:id'. Omit to remove ALL reactions on the message.
user_idNoRemove only this user's reaction for the given emoji. Requires emoji to be set.
channel_idYesID (snowflake) of the channel or thread containing the message.
message_idYesID of the message to remove reactions from.
Behavior4/5

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

Adds permission requirement context beyond annotations (destructiveHint=true). Does not mention rate limits or other side effects, but annotations cover core safety traits.

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?

Concise, front-loaded with main purpose, no wasted words. Efficiently covers modes, permissions, and alternatives.

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

Completeness5/5

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

Complete for a removal tool with 4 parameters and no output schema. Covers all usage scenarios and permission requirements. Annotations already handle destruction and idempotency.

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

Parameters4/5

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

Schema coverage is 100%, but description adds behavioral semantics for omitting emoji vs providing emoji vs emoji+user_id, which goes beyond the schema's parameter 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?

Description clearly states 'Remove reactions from a message' and explains three distinct modes (all, by emoji, by emoji+user). Distinguishes from sibling discord_add_reaction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use each mode and that removing all/another's reaction requires Manage Messages permission. Provides sibling alternative: 'Use discord_add_reaction to add.'

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

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