Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

React to a message with an emoji

react_to_message

Attach an emoji reaction to a WhatsApp message, or remove one.

Pass a single emoji character, e.g. πŸ‘. Passing an empty string removes the reaction this number previously left. A new emoji replaces this number's previous reaction rather than adding beside it; to bring the earlier one back, react with it again.

Works on messages in either direction: reacting to something a customer sent is often a cheaper acknowledgement than a reply.

The number first appears online and its unread messages in that conversation are marked as read, then the reaction is sent. Opening the conversation this way is automatic and uses no quota of its own.

Needs a plan that includes reactions. On a plan that does not, this answers payment_required: feature_not_available, and the answer will not change by retrying.

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

Input Schema

NameRequiredDescriptionDefault
emojiYesA single emoji, for example `πŸ‘`. An empty string removes the reaction this number left before.
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, non-idempotent, open-world write; the description goes well beyond by disclosing that the number first comes online and unread messages in that conversation get marked as read, and that this consumes no quota. It also documents the plan-gating failure mode `payment_required: feature_not_available` and that retrying will not help, which is exactly the kind of behavior an agent needs before calling.

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 the core action and the emoji-replacement rule, then the side effects, then the plan gate β€” a sensible order. It is somewhat long for three parameters and repeats the empty-string removal twice (description and schema), but no paragraph is filler.

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 write tool with an output schema, it covers mutation semantics (replace, remove), hidden side effects (coming online, marking read), quota impact, and the plan-based error response. Nothing an agent needs in order to call it correctly or interpret a failure 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 emoji and message_id semantics are already documented in the schema, and the description largely restates the empty-string removal rule. It does add meaning for the default number alias through the 'number comes online' side effect, but the parameter-level gain is marginal beyond the schema 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: attach or remove an emoji reaction on a WhatsApp message. It is clearly distinguishable from reply_to_message and delete_message, and the phrase 'cheaper acknowledgement than a reply' seals the distinction.

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?

Gives practical when-to-use guidance ('reacting to something a customer sent is often a cheaper acknowledgement than a reply') and explains the removal path via an empty string. It stops short of explicitly naming a sibling to use instead for deletion or replies, so it is strong but not a full when/when-not/alternative map.

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.