discord-mcp-server

add_reaction

Adds an emoji reaction to a specific message in a Discord channel using channel and message IDs. This tool enables bots to interact with Discord content programmatically.

Instructions

Ajoute une réaction emoji

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": "add_reaction"
  }
}

Input Schema

Name	Required	Description
`channelId`	Yes	ID du canal
`messageId`	Yes	ID du message
`emoji`	Yes	Emoji

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('add') which implies a write operation, but doesn't disclose behavioral traits like permission requirements, rate limits, whether it's idempotent, or what happens on failure. The description is minimal and lacks critical context for safe invocation.

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?

The description is a single, efficient sentence in French with zero waste. It's appropriately sized for a simple tool and front-loaded with the core action. Every word earns its place.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, error details) or behavioral constraints. For a write operation with three parameters, more context is needed for reliable agent use.

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%, with all three parameters (channelId, messageId, emoji) documented in the schema. The description doesn't add any meaning beyond the schema, such as emoji format examples or ID sourcing. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Ajoute une réaction emoji' clearly states the action (add) and resource (emoji reaction) in French. It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like 'edit_message' or 'create_button' which might also involve message interactions.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing message and channel IDs), exclusions, or related tools like 'edit_message' for modifying reactions. Usage is implied but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server