whatsapp_messages_write

Mark messages as read in a chat. Requires chat_jid. Optional message_id (marks up to this message; omit to mark all unread).

Bulk support: accepts message_ids for batched execution.

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": {
      "chat_jid": "<chat_jid>"
    },
    "name": "whatsapp_messages_write"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`chat_jid`	Yes
`message_id`	No
`message_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate readOnly=false and destructiveHint=false, which aligns with the mutation described. The description adds behavioral context (e.g., omit message_id to mark all unread) and mentions a requirement (chat_jid), going beyond annotations without contradiction.

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?

The description is compact and direct, two sentences with no redundant information. It efficiently conveys the operation and key parameters.

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?

The description is sufficient for the tool's simplicity. It covers the operation, required/optional parameters, and bulk behavior. No output schema exists, so return values are not expected. Error handling isn't mentioned, but this is acceptable given the tool's scope.

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 descriptions are absent, but the description explains chat_jid (required), message_id (optional, marks up to), and message_ids (bulk). The 'account' parameter is not explained, so coverage is partial but covers the core semantics.

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 clearly states the action: 'Mark messages as read in a chat.' This is specific and distinguishes from sibling tools like whatsapp_send_text or whatsapp_message_delete.

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?

Provides clear usage details: requires chat_jid, optional message_id to mark up to a specific message or omit to mark all unread, and bulk support via message_ids. It doesn't explicitly compare to alternatives but the intent is evident.

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

All WhatsApp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.