Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Mark a WhatsApp conversation as read

mark_as_read

Mark a conversation's unread messages as read, without sending anything.

Set exactly one recipient: number, group_id, or contact_id. With number or contact_id, only the one-to-one chat with that person is marked as read: the messages they sent in groups stay unread. For a group, pass its group_id.

This is independent of the automatic mark-as-read that already happens when you send, reply, react, edit, delete or start typing (the number also appears online first): use it to clear an unread badge on its own, for example when handing a conversation to a human who has already seen it. No message is sent and no message.* event is produced, but the sender sees the messages as read (blue ticks) on WhatsApp.

Needs a plan that includes read receipts (BUSINESS and above). Without it this answers payment_required: feature_not_available, and the answer will not change by retrying.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mark_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberNoRecipient phone number in E.164 form, digits only, country code first (e.g. `5511999999999`). Set exactly one of `number`, `group_id` or `contact_id`.
group_idNoRecipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that.
contact_idNoRecipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
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. Changed2 schema fields changed
    • changedInput schema / properties / contact_id / description
      Previous value: -"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one inbox does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."New value: +"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."
    • changedInput schema / properties / group_id / description
      Previous value: -"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one inbox does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that."New value: +"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses that no message is sent, no message.* event fires, and the sender sees blue ticks — plus a plan gate that returns payment_required: feature_not_available with no benefit from retrying. The idempotentHint=false claim is not addressed, and the description does not say whether marking an already-read chat is a no-op, which is the one behavioral gap.

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-loads the core action and the recipient rule before the longer behavioral notes, and each paragraph has a distinct job (what it does, recipient selection, relationship to automatic marking, plan requirement). The parenthetical about the number appearing online first is a minor digression that slightly dilutes an otherwise tight structure.

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 four-parameter tool with an output schema, the description covers the action, recipient disambiguation, side effects and event absence, and the exact failure mode and error code for plan-gated usage. An agent has everything needed to decide to call it and to interpret a payment_required response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: with number or contact_id only the one-to-one chat is cleared and group messages from that person stay unread, while a group requires its group_id. It restates the 'set exactly one recipient' rule already in the schema, which keeps it from a 5.

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?

Opens with a specific verb and resource ('Mark a conversation's unread messages as read') and immediately scopes it with 'without sending anything.' It is clearly distinguishable from the send/reply/react siblings, which it names as the source of the automatic mark-as-read.

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?

States both when to use it ('clear an unread badge on its own, for example when handing a conversation to a human who has already seen it') and when it is unnecessary, because sending, replying, reacting, editing, deleting or typing already marks read. The relationship to alternative behavior is explicit rather than inferred.

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.