Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_user_reaction

Destructive

Remove another user's reaction from a Discord message, requiring Manage Messages permission.

Instructions

Remove another user's reaction (needs Manage Messages). [DELETE /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/{reaction_type}/{user_id}]

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>",
      "user_id": "<user_id>"
    },
    "name": "remove_user_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesEmoji: unicode (e.g. 👍) or custom as name:id (e.g. blobwave:123456789)
user_idYesUser ID
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID
reaction_typeNoReaction type: 0 = normal, 1 = super reaction (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the mutation and its risk are known. The description contributes the Manage Messages permission requirement, which is real added context, but says nothing about irreversibility, behavior when the reaction/user doesn't exist, or super-reaction handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence carries the action and the permission gate, with the endpoint appended as compact technical context. Nothing is padded, though the endpoint string is somewhat redundant with the name and schema.

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 single-target delete with no output schema, the definition covers what is removed and the authorization needed, which is sufficient to call it correctly. It is thin on failure modes (missing reaction, invalid emoji format) but not deficient for a tool of this complexity.

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%, including the emoji format and reaction_type meaning, so the surviving baseline of 3 applies. The endpoint path does hint at parameter ordering and that reaction_type/reaction_type/user_id are path segments, but the description adds no new semantics about individual parameters.

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 a specific verb and resource ('Remove another user's reaction') and the qualifier 'another user's' cleanly separates it from the sibling remove_own_reaction. The bracketed DELETE endpoint reinforces exactly which object is mutated.

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 concrete prerequisite that tells an agent when this call will succeed versus fail. However, it never states when to prefer this over add_reaction, remove_all_reactions, or remove_all_reactions_for_emoji, leaving alternative selection to inference.

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