Skip to main content
Glama
PaSympa

discord-mcp

by PaSympa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

discord_get_reactions

Read-only

List Discord users who reacted to a message with a specific emoji, returning their ID, username, and bot status. Use this read-only tool to identify reactors quickly.

Instructions

List the users who reacted to a message with a specific emoji. Returns { reactions: [...] } with id, username, bot flag. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiYesUnicode emoji or custom emoji 'name:id' to list reactors for.
limitNoMax users to return (1–100). Default 25.
channel_idYesID (snowflake) of the channel or thread containing the message.
message_idYesID of the message to inspect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reactionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed7 schema fields changedv2.0.0
    • addedInput schema / properties / channel_id / pattern
      Added value: +"^\\d{17,20}$"
    • addedInput schema / properties / limit / default
      Added value: +25
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / message_id / pattern
      Added value: +"^\\d{17,20}$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "reactions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "bot": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "username": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "username",
+          "bot"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "reactions"
+  ],
+  "type": "object"
+}
  3. Changed4 schema fields changedv1.6.0
    • addedInput schema / properties / channel_id / description
      Added value: +"ID (snowflake) of the channel or thread containing the message."
    • changedInput schema / properties / emoji / description
      Previous value: -"Unicode emoji or custom emoji 'name:id'."New value: +"Unicode emoji or custom emoji 'name:id' to list reactors for."
    • changedInput schema / properties / limit / description
      Previous value: -"1–100, default 25."New value: +"Max users to return (1–100). Default 25."
    • addedInput schema / properties / message_id / description
      Added value: +"ID of the message to inspect."
  4. Addedv1.5.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description repeats 'Read-only' and mentions the return shape. It does not add deeper behavioral context such as pagination behavior, rate limits, or what happens when no users have reacted, though the annotations and output schema cover the safety and return aspects.

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 two sentences with no wasted words; the main purpose is front-loaded and the additional read-only note is brief.

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

Completeness5/5

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

For a simple read-only list tool with a full input schema and an output schema, the description provides enough context for correct invocation. No important behavioral or invocation detail is missing.

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. The description adds no additional parameter semantics beyond what the schema provides, matching the baseline for high schema coverage.

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 description uses a specific verb ('List') tied to a clear resource (users who reacted to a message with a specific emoji). It also distinguishes itself from reaction-mutating siblings like discord_add_reaction and discord_remove_reactions by emphasizing a read-only listing operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear context of when to call this tool: to inspect which users reacted to a message with a given emoji. It does not explicitly name alternatives or exclusion conditions, but the read-only framing implicitly rules out mutation tools.

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