Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Mark WhatsApp message as read

mark_as_read

Mark an incoming WhatsApp message as read (blue ticks) using its wamid, with an option to display a typing indicator. Use it to acknowledge received messages and signal that a reply is being prepared.

Instructions

Mark an incoming message as read (blue ticks), optionally also showing a typing indicator. Pass the wamid of the message you received.

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>"
    },
    "name": "mark_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYeswamid of the incoming message
show_typingNoAlso show a typing indicator to the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The description adds useful context beyond the sparse annotations (openWorldHint, destructiveHint=false): it discloses that read receipts appear as blue ticks in the user's chat and that a typing indicator can be shown. It does not cover error behavior for unknown/expired wamids, rate limits, or whether the call is idempotent.

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?

Two short sentences, front-loaded with the action and its visible effect, then the required identifier. No filler or repetition beyond the single wamid reference needed for emphasis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter action with no output schema, the description covers the essentials (what it does, what to pass, optional typing indicator) but omits where the wamid comes from and what happens on failure, leaving a small but real gap for an agent operating in a messaging flow.

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% and both parameters are already documented, including 'wamid of the incoming message'. The description restates 'Pass the wamid of the message you received' but adds no format (e.g. prefix, length) or source for obtaining it, so baseline 3 applies.

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 ('Mark an incoming message as read') plus the user-visible effect ('blue ticks'), which cleanly separates it from the send_* siblings that create outbound messages rather than acknowledge inbound ones.

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?

The word 'incoming' and 'the message you received' imply the use case is acknowledgement of a received message, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g. when to reply with send_text_message instead).

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