Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

React to a WhatsApp message

react_to_message
Idempotent

Add or remove a single emoji reaction on a WhatsApp message using its message ID and emoji; pass an empty emoji to remove it.

Instructions

React to a message with one emoji, or pass "" to take your reaction off.

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
emojiYes
account_idNo
message_idYes

Output Schema

NameRequiredDescriptionDefault
emojiYes
account_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed4 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
    • removedInput schema / properties / emoji / description
      Removed value: -"A single emoji such as \"👍\", or \"\" to remove your reaction"
    • removedInput schema / properties / message_id / description
      Removed value: -"Message id from read_messages / search_messages / get_message, e.g. \"false_4072...@s.whatsapp.net_3EB0...\""
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "account_id": {
      +      "type": "string"
      +    },
      +    "emoji": {
      +      "type": "string"
      +    },
      +    "message_id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "emoji",
      +    "account_id"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. First observedv0.9.3

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavior — that an empty string removes the existing reaction and that only one emoji is allowed — but says nothing about replacing an existing reaction, permission requirements, or network/rate-limit behavior for an open-world call.

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?

A single tight sentence with zero filler, front-loading the primary action before the removal edge case. Nothing could be cut without losing meaning.

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?

An output schema exists, so return values need not be described. For a simple three-parameter reaction tool, the description covers the action and the one surprising input case; the remaining gaps (message_id/account_id meaning) are minor.

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 0% across three parameters, so the description must compensate. It usefully defines the emoji parameter's non-obvious empty-string-removal semantics and the single-emoji limit, but message_id and account_id receive no explanation at all.

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?

The description states a specific verb and resource ("react to a message") with a concrete constraint (one emoji), which distinguishes it from siblings like send_message or edit_message. It stops short of explicitly naming or contrasting any alternative, so it lands just below the top tier.

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 implied rather than stated: an agent can infer this is the tool for emoji reactions and, notably, that passing "" removes a reaction. There is no explicit when-to-use/when-not guidance and no reference to alternatives such as edit_message or send_message.

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