Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

remove_own_reaction

Destructive

Removes your own reaction from a Discord message by specifying the channel ID, message ID, emoji, and optional reaction type.

Instructions

Remove your own reaction from a message. [DELETE /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/{reaction_type}/@me]

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

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
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.6/5.0
Behavior3/5

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

Annotations already declare this as a non-readOnly, destructive, open-world operation, so the safety profile is covered. The description adds the REST endpoint, confirming it is a targeted DELETE on a single reaction, and 'your own' clarifies that only the caller's reaction is affected. It does not disclose behavior on missing reactions or repeat calls.

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?

Two short elements — a one-sentence action statement followed by the endpoint in brackets — with the action front-loaded and nothing padded. The bracketed endpoint is somewhat redundant but earns its place by anchoring parameter placement.

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 four-parameter DELETE with full schema coverage, existing annotations, and no output schema, the description is sufficient to invoke the tool correctly. Only edge-case behavior (nonexistent reaction, idempotency) is left unaddressed.

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?

Schema description coverage is 100%, so the baseline is 3, and the endpoint path in the description maps path parameters to their roles (channel_id, message_id, emoji, reaction_type) in a way the schema does not. It does not add format or default details for reaction_type beyond what the schema already states.

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?

The description states a specific verb and resource ('Remove your own reaction from a message') and the 'your own' qualifier scopes it away from removing other users' reactions or bulk removals. It never names a sibling tool explicitly, so an agent must infer the distinction from the scope word alone.

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?

Usage is only implied: 'your own' signals this is for self-removal rather than moderation of others, which weakly distinguishes it from remove_user_reaction and remove_all_reactions. There is no explicit statement of when to prefer this over those siblings, nor any precondition guidance.

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