Skip to main content
Glama
discord-self-mcp

discord-self-mcp

by rawnullbyte

discord_remove_reaction

Removes your Discord account's reaction from a specific message by channel ID, message ID, and emoji. Use it to undo a reaction or clean up message interactions.

Instructions

Remove one of the account's reactions from a message.

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": {
      "channelId": "<channelId>",
      "messageId": "<messageId>",
      "emoji": "<emoji>"
    },
    "name": "discord_remove_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYes
channelIdYesDiscord id (snowflake)
messageIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose one useful constraint — only the account's own reaction can be removed — but says nothing about required permissions (MANAGE_MESSAGES / READ_MESSAGE_HISTORY), what happens when the reaction is absent, or whether the call is idempotent. For a mutation tool with zero annotation coverage this is a substantial gap.

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 with no filler or redundancy. It is efficiently written, though there is no structure (no parameter hints or caveats) because the content is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-parameter mutation tool with no annotations and no output schema, the description is too thin. The emoji encoding question, the permission requirement, and the behavior when no matching reaction exists are all left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: channelId is documented as a snowflake and messageId inherits that via $ref, but `emoji` has no format guidance at all. That is the single most error-prone parameter here (unicode character vs. custom emoji `name:id` vs. URL-encoded form), and the description adds nothing about it, so the low-coverage gap is left unfilled.

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 ('Remove') and resource ('reaction from a message') and adds a meaningful scope qualifier: it removes one of the *account's own* reactions, not arbitrary users' reactions. That distinction is clear enough to separate it from the role/timeout/message-mutation siblings. It does not explicitly name or route away from any alternative, which keeps it at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as removing someone else's reaction or clearing all reactions. Usage is only inferable from the tool name and the word 'Remove'. Nothing tells the agent when this call will fail or when a different tool is required.

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