Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Get per-recipient delivery and read receipts

get_message_receipts
Read-onlyIdempotent

See who received and who read a WhatsApp message.

Most useful for group messages, where the single status on the message cannot express that some members read it and others have not.

Requires a plan that includes read receipts; on plans without it the call is refused with feature_not_available, which no retry will fix.

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": "get_message_receipts"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the call is gated on a plan feature and fails with `feature_not_available` in a way that retrying cannot fix, which prevents a wasteful retry loop.

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?

Three short paragraphs: what it does, when it matters, and the failure mode to expect. Purpose is front-loaded and no sentence is redundant.

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 shape need not be described, and both parameters are fully documented in the schema. Combined with the plan-gating warning and group-message framing, nothing an agent needs to call this correctly 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 description coverage is 100%, with message_id and number_alias both documented including format hints (`msg_…`, `num_…`) and the list_numbers pointer. The description adds no parameter meaning on top of that, 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 ('See who received and who read a WhatsApp message') and immediately scopes it against the message-level status that siblings like get_message_status would return. An agent can tell what this returns (per-recipient receipts) without opening the schema.

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 explicit selection context: 'Most useful for group messages, where the single status on the message cannot express that some members read it and others have not.' That is a clear when-to-use condition, though it stops short of naming a specific alternative tool for the 1:1 case.

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.