Skip to main content
Glama
Sign In
Guildora

Guildora

by az-xx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove a reaction

remove_reaction
Idempotent

Removes a reaction from a Discord message, defaulting to the bot's own reaction or another member's with Manage Messages permission.

Instructions

Removes a reaction from a message: the bot's own by default, or another member's (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": {
      "message": "<message>",
      "emoji": "<emoji>"
    },
    "name": "remove_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoInstead of channel: a user (ID, <@mention> or name) whose DM channel to use.
emojiYesUnicode emoji ("👍") or a server emoji ("<:name:id>", ":name:", name or ID).
guildNoServer ID or name. Optional if DISCORD_GUILD_ID is set or the bot is in one server.
memberNoWhose reaction to remove (ID, mention or name). Default: the bot.
channelNoChannel or thread: ID, <#mention>, link, or name. Archived threads by ID or link.
messageYesMessage ID or message link (https://discord.com/channels/...). With a link, channel is optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety and idempotency (destructiveHint=false, idempotentHint=true), and the description adds genuinely new operational context: the default target is the bot's own reaction and removing someone else's requires Manage Messages. It does not explain what happens when the reaction is absent, but the idempotent annotation already implies that.

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?

A single sentence with zero filler, front-loading the action and then the two target modes with the permission caveat inline.

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 six-parameter tool with full schema coverage, annotations, and no output schema, the description supplies the key operational facts (default target, permission gate). Return behavior is left unstated, but that is a minor gap given the annotation set.

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 all six parameters are already documented, including the member default. The description's "bot's own by default" restates the schema's "Default: the bot" rather than adding new meaning, so the baseline applies.

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?

States a specific verb and resource ("Removes a reaction from a message") and immediately scopes the target (bot's own vs. another member's). It is clearly distinguishable from add_reaction by the verb, though it does not name the sibling explicitly.

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?

Gives clear context for the two cases: default removal of the bot's own reaction, and removal of another member's which requires Manage Messages. It does not state exclusions or name alternatives, so it stops short of the top score.

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