Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

React to a WhatsApp message

react_to_message

Add an emoji reaction to a WhatsApp message or remove your own by passing an empty string, using the target message id and optional account.

Instructions

Add an emoji reaction to a message, or pass an empty string to remove your reaction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emojiYesA single emoji such as "👍", or "" to remove your reaction
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
message_idYesMessage id from read_messages / search_messages / get_message, e.g. "false_4072...@s.whatsapp.net_3EB0..."

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.9.3

TDQS

A3.6/5.0
Behavior3/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the agent knows this is a non-destructive mutation. The description's one notable behavioral addition, that an empty string removes the reaction, is already duplicated in the schema parameter description. It adds no auth, rate-limit, or return-value context beyond what structured fields supply.

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 well-formed sentence that front-loads the primary action and includes the removal case with zero padding. Nothing is wasted.

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 simple 3-parameter mutation with no output schema, the description plus the 100%-covered schema convey everything needed to call it correctly. Only minor gaps remain (no mention of account context or response behavior on success/failure), which are low-stakes here.

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 three parameters (emoji, account_id, message_id) are fully documented in the schema, including the empty-string removal trick and account resolution fallback. The description adds no syntax or semantic detail beyond that, so the baseline of 3 is appropriate.

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+resource ('add an emoji reaction to a message') and includes the inverse operation (removal), making the tool's scope unambiguous. It does not explicitly name a sibling tool, but the reaction semantics are specific enough to distinguish it from send_message or edit_message.

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 by the description ('add an emoji reaction' / pass empty string to remove), which effectively tells an agent how to invoke both modes. However, there is no explicit guidance about when to use this versus alternatives like send_message, nor any prerequisites or account resolution notes.

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