Skip to main content
Glama

Who reacted to a message

get_reactions
Read-only

List the reactions on a message and identify who reacted, including [me] for the user, so you can count emojis like 👍 and see participants.

Instructions

List the reactions on a message with the names of the people who reacted ([me] for the user), e.g. to count the 👍 on "who's in for Saturday?". Message IDs appear in get_new_messages lines (#id) and in the official Beeper MCP.

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": {
      "chatID": "<chatID>",
      "messageID": "<messageID>"
    },
    "name": "get_reactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIDYesChat ID (or local chat ID)
messageIDYesID of the message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral detail beyond that: the result includes reactor names and substitutes [me] for the calling user. It says nothing about ordering, pagination, or what happens when a message has no reactions, so it adds moderate value rather than rich context.

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?

Two sentences, front-loaded with the action and result shape, followed by a grounding example and the ID sourcing note. Dense but every element earns its place; no filler.

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 two-parameter read tool with no output schema, the description covers the essentials: what is returned (reactor names plus a [me] marker) and where the required messageID may be obtained. Only minor gaps remain, such as whether the reaction list is ordered or grouped by emoji.

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 100%, so both chatID and messageID are already documented, giving a baseline of 3. The description does add one useful semantic hint by telling the agent that message IDs come from '#id' patterns in get_new_messages output, but it does not explain the chatID/local-chat-ID distinction beyond the schema.

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?

Specific verb and resource: 'List the reactions on a message with the names of the people who reacted.' It also states what the payload contains (reactor names, a [me] marker for the caller), which lets an agent distinguish this from the sibling 'react' that adds reactions. It stops short of explicitly naming that sibling as the counterpart, so it is not a full 5.

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?

Provides a concrete use case ('to count the 👍 on "who's in for Saturday?"') and tells the agent where message IDs come from (get_new_messages lines, and the official Beeper MCP). No explicit when-not-to-use or named alternative, but the context needed to select this tool is present.

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