Skip to main content
Glama
Sign In
Capes

Capes

by Dipeshpal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

discord_remove_reaction

Destructive

Remove a bot's, a specific user's, or all reactions from a Discord message by providing channel ID, message ID, emoji, user ID, or clear_all. Requires Manage Messages to remove others' reactions.

Instructions

Remove the bot's reaction, another user's reaction (user_id), or all reactions on the message (clear_all). Removing others' reactions needs Manage Messages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>"
    },
    "name": "discord_remove_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiNoUnicode or name:id. Not needed with clear_all.
user_idNoRemove this user's reaction instead of the bot's
clear_allNoRemove every reaction from the message
channel_idYesChannel ID (a thread ID also works)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so safety is covered. The description adds genuinely useful info beyond that: the Manage Messages authorization requirement for removing other users' reactions. It does not explain irreversibility or the response, but the auth requirement is a meaningful addition.

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?

One sentence covers all three modes plus the permission caveat, with the modes front-loaded and no filler. Every clause earns its place.

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

Completeness4/5

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

For a destructive, no-output-schema mutation tool the description covers the full set of behaviors and the key authorization constraint. It omits secondary details (reversibility, channel/thread nuances already in schema) but nothing critical to correct invocation is missing.

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 coverage is 100%, so every parameter is already documented — including that emoji is not needed with clear_all and that user_id targets another user's reaction. The description's parameter mapping largely restates the schema, so it earns the baseline rather than more.

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?

Names the specific verb (remove) and resource (reaction) and enumerates the three distinct modes — the bot's reaction, another user's via user_id, or all via clear_all. It is clearly separable from its siblings discord_add_reaction and discord_list_reactions.

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

Usage Guidelines4/5

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

Explains which mode each parameter selects and states the prerequisite for the privileged path ('Removing others' reactions needs Manage Messages'). No explicit when-not guidance or alternative routing, but the condition for the restricted operation is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools