Skip to main content
Glama

messages_react

Destructive

Put an emoji reaction (👍, ❤️, 🔥, 😂, 🙏 ...) on a message, as the connected account, or take one back with remove=true. Use it where a short acknowledgement fits better than a reply.

Get the message_id from messages.read_history (the message must be in the given thread). Works on channels that support reactions: Telegram user accounts, Telegram bots (in a group only when the bot is an administrator; a bot holds one reaction per message, a new one replaces it) and WhatsApp personal numbers; any other channel is refused with the reason, nothing is sent. Telegram accepts only its own set of reaction emoji (a group may narrow it further) and refuses others.

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": {
      "thread_id": "<thread_id>",
      "message_id": "<message_id>",
      "emoji": "<emoji>"
    },
    "name": "messages_react"
  }
}

Input Schema

NameRequiredDescriptionDefault
emojiYesOne emoji, e.g. 👍 or ❤️. With remove=true, the emoji to take back.
removeNotrue takes back this account's reaction instead of putting it. OMIT to put the reaction.
thread_idYesThread containing the message (numeric DB id or channel_ref).
message_idYesThe message to react to: its id from messages.read_history.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds substantial context beyond them: unsupported channels are refused with a reason and nothing is sent, bots hold one reaction per message so a new one replaces the old, and admin status is required in groups. It does not, however, explain what the destructive flag actually means for reactions (e.g. whether a reaction can be silently overwritten on a bot channel), leaving a small gap against the annotation.

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?

Front-loaded with purpose and the inverse operation, then prerequisites, then channel support, then emoji constraints — no filler sentences. It is dense with parentheticals (bot admin rule, one-reaction-per-message rule) that read slightly run-on but each carries real calling information.

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?

No output schema exists, and the description compensates by stating what happens on failure (refused with reason, nothing sent), which is the only return behavior an agent needs to reason about. Combined with channel and emoji restrictions, nothing required to call it correctly 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 coverage is 100%, so the schema already documents emoji, remove, thread_id, message_id and in_workspace. The description adds useful constraints the schema lacks — Telegram's restricted emoji set, possible per-group narrowing, and the fact that the emoji field is the one taken back when remove=true — but does not touch thread_id/in_workspace semantics, so it lands at baseline.

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 specific verb and resource ('Put an emoji reaction on a message') and covers the inverse operation ('take one back with remove=true'), which cleanly separates it from messages_send and messages_edit. An agent knows exactly what this tool does without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says when to prefer it ('where a short acknowledgement fits better than a reply'), names the prerequisite source for message_id (messages.read_history, message must be in the given thread), and enumerates which channel types accept it versus which are refused. That is both when-to-use and when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.