Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

react

Add one or more emoji reactions to a Discord message using its link or channel and message IDs, with optional super (burst) reactions.

Instructions

React to a message by link (or channel_id + message_id) with one or more emojis.

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": {
      "message": "<message>",
      "emojis": "<emojis>"
    },
    "name": "react"
  }
}

Input Schema

NameRequiredDescriptionDefault
superNoSuper (burst) reaction
emojisYesUnicode emojis or custom name:id
messageYes
channel_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, establishing the safety profile. The description adds nothing beyond restating the mutation: no note on idempotency for duplicate reactions, no mention of permission requirements, and no hint about what happens when the emoji is invalid or the message is unreachable.

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 no filler; the addressing alternatives are packed into a parenthetical rather than a second sentence. Every clause carries information.

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?

For a four-parameter mutation tool with annotations and no output schema, the description covers the what and the addressing scheme but omits permission prerequisites, duplicate-reaction behavior, and error outcomes. Adequate as a minimum, but thin for a write operation.

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 50% and both 'message' and 'channel_id' lack schema descriptions, so the description's clarification that 'message' accepts a link or is paired with channel_id fills a real gap. However, it names 'message_id' while the schema parameter is 'message', and adds no format detail (link shape, ID type), leaving residual ambiguity.

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 uses a specific verb ('React') plus resource ('a message') and enumerates the two acceptable addressing forms, so an agent knows exactly what operation this performs. It does not distinguish itself from nearby siblings such as add_reaction, leaving ambiguity about which reaction tool to pick.

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 statement of when to use this tool versus alternatives, no prerequisites (membership, permissions), and no guidance on failure cases. The parenthetical '(or channel_id + message_id)' is an input-selection hint rather than usage guidance, so the description only implicitly suggests its purpose.

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