MCP Discord Bot Server

discord_add_reaction

Add an emoji reaction to a Discord message using its channel ID, message ID, and chosen emoji, returning JSON confirmation.

Instructions

Add an emoji reaction to a Discord message.

Args:
    channel_id: The ID of the channel containing the message.
    message_id: The ID of the message to react to.
    emoji: The emoji to react with (Unicode or Discord custom emoji format).

Returns:
    JSON confirmation of the reaction being added.

Input Schema

TableJSON Schema

Name	Required	Description
`emoji`	Yes	The emoji to react with. Use standard Unicode emojis (e.g., '👍', '❤️') or Discord custom emoji format. Required.
`channel_id`	Yes	The ID of the Discord channel containing the message. Required.
`message_id`	Yes	The ID of the message to add a reaction to. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 7, 2026

TDQS

A3.5/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 the full transparency burden for a write operation. It discloses only that a JSON confirmation is returned (largely redundant with the existing output schema) and says nothing about required permissions (e.g., ADD_REACTIONS), idempotency of duplicate reactions, or rate limits.

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?

The core purpose is front-loaded in a single clear sentence, followed by a compact Args/Returns block. Structure is clean, though the parameter lines duplicate the schema and slightly inflate length for a three-parameter tool.

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?

With an output schema present, return values need not be re-explained, and the input schema is fully documented, so the description is functionally sufficient for calling the tool. The one gap is authorization/permission context for a mutation, which the absence of annotations leaves unaddressed.

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 three parameters are already documented in the schema, including emoji format examples and required flags. The description's Args block restates the same meaning without adding syntax or edge-case detail beyond it, matching the baseline for fully-covered schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb (add) and resource (emoji reaction on a Discord message), which no sibling tool duplicates. An agent can immediately distinguish this from message-sending or pinning siblings.

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 by the tool's obvious purpose; there is no explicit statement of when to use it, when not to, or what to do instead. For a self-evident single-purpose action with no competing sibling, this is adequate but unguided.

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

Deploy Server