Skip to main content
Glama
Sign In
discord-mcp

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_remove_reactions

DestructiveIdempotent

Remove all reactions from a message, filter by emoji, or delete a specific user's reaction. Manage Messages permission needed to remove all or other users' reactions.

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.

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_reactions"
  }
}

Input 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / user_id / pattern
      Added value: +"^\\d{17,20}$"
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread containing the message."
    • changedInput schema / properties / emoji / description
      Previous value: -"Unicode emoji or custom emoji 'name:id'. Omit to remove all reactions."New value: +"Unicode emoji or custom emoji 'name:id'. Omit to remove ALL reactions on the message."
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the message to remove reactions from."
    • changedInput schema / properties / user_id / description
      Previous value: -"Remove only this user's reaction for the given emoji."New value: +"Remove only this user's reaction for the given emoji. Requires emoji to be set."
  4. Addedv1.5.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint and readOnlyHint annotations, the description discloses exactly what gets destroyed in each mode, including the all-reactions case. It also exposes the Manage Messages permission requirement for removing all reactions or another user's reaction, adding meaningful behavioral context the annotations do not carry.

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?

Every sentence carries distinct information: core purpose, the three scope variants, the permission caveat, and the sibling routing sentence. It is front-loaded with the main action and uses compact parallel phrasing with no redundant filler.

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?

For a destructive reaction tool with no output schema, the description covers all necessary call decisions: which parameters to include, what each combination removes, and when elevated permission is required. The annotations fill in the remaining idempotency and destructiveness context.

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?

The schema already documents all four parameters at 100% coverage, so the baseline is 3. The description adds value by defining the legal combinations of emoji and user_id and their effects, which the parameter descriptions alone only partially convey.

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 opens with a specific action and object, 'Remove reactions from a message,' and then breaks out the exact scope variants: all reactions, one emoji, or one user's reaction. It also names the related sibling discord_add_reaction, making the tool's purpose easy to distinguish from the add operation.

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?

The three parameter combinations are explicitly mapped to three removal behaviors, and the permission requirement for the destructive variants is stated. The final sentence tells the agent to use discord_add_reaction when the intent is to add rather than remove, providing a clear routing rule.

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