Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

add_reaction

React to a Discord message with a Unicode or custom emoji to acknowledge, vote, or flag content.

Instructions

React to a message with an emoji (unicode like 👍 or custom name:id). [PUT /channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@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": "add_reaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo0 normal, 1 super reaction (burst)
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this is a non-destructive write against an external service. The description usefully discloses the HTTP method and endpoint path, which implies an authenticated self-scoped write. It does not mention idempotency (re-adding the same reaction being a no-op) or required permissions, which would have raised the score.

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 plus a bracketed endpoint reference, with no wasted wording. The endpoint bracket is compact and informative rather than filler. Minor deduction only because the emoji-format detail duplicates what the schema already says.

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

Completeness3/5

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

With full schema coverage and annotations covering safety, the essential contract is present and there is no output schema to explain. It falls short of 'complete' because it omits the optional super-reaction flag at the description level and says nothing about idempotent behavior or channel access requirements.

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%, so all four parameters are already documented, including the emoji format and the 'type' field's 0/1 meaning. The description restates the emoji format rather than adding new meaning, 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?

The description states a specific verb and resource — reacting to a message with an emoji — and adds concrete emoji formats (unicode like 👍 or custom name:id). The parenthetical REST endpoint pins down exactly which operation is performed (@me, i.e. the acting user's own reaction). It does not, however, differentiate itself from the sibling tool literally named 'react', leaving the agent to infer the distinction.

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 explicit when-to-use guidance and no named alternatives. The agent is not told to use this rather than 'react', 'remove_own_reaction', or 'remove_user_reaction', nor are prerequisites (e.g., having access to the channel) stated. Usage is only implied by the verb.

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