Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_all_reactions_for_emoji

Destructive

Remove all reactions of a specified emoji from a Discord message using channel, message, and emoji identifiers; requires Manage Messages permission.

Instructions

Remove all reactions of one emoji from a message (needs Manage Messages). [DELETE /channels/{channel_id}/messages/{message_id}/reactions/{emoji}]

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>",
      "emoji": "<emoji>"
    },
    "name": "remove_all_reactions_for_emoji"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesEmoji: unicode (e.g. 👍) or custom as name:id (e.g. blobwave:123456789)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is supplied. The description adds genuinely new context in the form of the required Manage Messages permission and the exact REST endpoint. It does not state that other users' reactions are affected and that the operation cannot be undone, which is the remaining behavioral gap for a destructive bulk delete.

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 front-loaded sentence with the permission requirement inline and the endpoint bracketed at the end. No filler, and the action and scope land before any ancillary detail.

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 simple three-parameter mutation with full schema coverage, full annotation coverage, and no output schema, the definition covers purpose, permission, and endpoint. Only the irreversibility and cross-user impact of the deletion are left unstated.

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%: the schema already documents emoji format (unicode or name:id), channel ID types, and message ID. The description adds no parameter-level meaning beyond that, so the baseline 3 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, resource, and scope: 'Remove all reactions of one emoji from a message.' The 'of one emoji' qualifier implicitly distinguishes it from remove_all_reactions (all emojis) and the single-user variants, though no sibling is named outright.

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

Usage Guidelines3/5

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

The parenthetical '(needs Manage Messages)' gives a real prerequisite, which is more than most definitions offer. However, there is no guidance on when to choose this over remove_all_reactions, remove_user_reaction, or remove_own_reaction, leaving the selection to inference from the names.

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