Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

list_reactions

Read-only

Retrieves the users who reacted to a specific Discord message with a chosen emoji, supporting pagination and normal or super reaction filters.

Instructions

List users who reacted to a message with an emoji. [GET /channels/{channel_id}/messages/{message_id}/reactions/{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": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>",
      "emoji": "<emoji>"
    },
    "name": "list_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo0 normal, 1 super reactions
afterNoReturn items after this ID (pagination)
emojiYesEmoji: unicode (e.g. 👍) or custom as name:id (e.g. blobwave:123456789)
limitNo1-100
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

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The endpoint path in the description adds useful context that this is a scoped Discord REST GET, but no rate-limit, pagination, or result-shape behavior is disclosed beyond that.

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?

One tight sentence plus the endpoint in brackets, front-loaded with the core action. No wasted words, though the bracketed path is developer-facing padding for an agent that already has the tool name.

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?

For a simple read tool with six fully described parameters, the definition covers what is needed to select and invoke it. The only gap is that there is no output schema and the description does not say whether the response is a list of user objects or reaction-count aggregates.

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 each parameter (emoji format, type 0/1, after, limit 1-100) already documented inline. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States a precise verb and resource: 'List users who reacted to a message with an emoji.' The REST endpoint path pins down the exact scope (per channel/message/emoji), which clearly separates it from siblings like remove_all_reactions and remove_all_reactions_for_emoji.

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 verb 'List'; there is no explicit statement of when to pick this over alternatives, no prerequisites, and no mention of pagination workflow despite the `after`/`limit` params. Adequate for a straightforward read, but guidance is left to inference.

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