Skip to main content
Glama

Read a sent message's status

get_message_status
Read-only

Read where one of the user's own messages stands, from the receipts WhatsApp sent about it: sent until the first receipt, then delivered to a phone, read, or played for a voice note or a video, with each recipient's own stages and when they happened (UTC). In a group, read the recipients: one of them reading is the whole status. Only a message the user sent in a conversation under capture has one; find it with search_messages, or use the message_id a send tool returned. A recipient who turned read receipts off never reports read.

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

Input Schema

NameRequiredDescriptionDefault
message_idYesThe message: the message_id search_messages or a send tool returned.
conversation_idYesThe conversation id (from the read tools).

Output Schema

NameRequiredDescriptionDefault
statusNosent, delivered, read or played: the furthest stage any recipient reached.
message_idNoThe message.
recipientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint=false, so the safety profile is covered; the description adds the real behavioral substance: the receipt-based state progression, per-recipient stages with UTC timestamps, the rule that in a group one reader defines the whole status, and that recipients with read receipts disabled never report 'read'. These are exactly the non-obvious traits that prevent misreading results. It stops short of describing polling behavior or whether statuses update over time, which is the only remaining 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?

The end-state enumeration and the group rule are front-loaded, and every sentence carries information an agent needs. There is minor redundancy where the message_id provenance is restated from the schema, but nothing is padded.

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?

With only two fully documented required parameters, read-only annotations, and an output schema handling return values, the description covers everything an agent needs: what is read, the state vocabulary, per-recipient semantics, group interpretation, timestamp timezone, preconditions, and the read-receipt opt-out caveat.

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 already carry descriptions identical in substance ('the message_id search_messages or a send tool returned', 'the conversation id (from the read tools)'). The description reiterates this provenance without adding syntax, format, or constraints beyond the schema, so the 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?

The description opens with a specific verb and resource: reading where one of the user's own sent messages stands, based on WhatsApp receipts. It enumerates the concrete states (sent, delivered, read, played) so the agent knows exactly what is returned, and it is clearly distinguishable from search_messages, which only finds the message.

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?

It states a precondition that excludes most messages ('Only a message the user sent in a conversation under capture has one') and gives two concrete routes to the required id: search_messages or the message_id returned by a send tool. That is explicit when-to-use, when-not-available, and where the inputs come from.

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.

Resources