Skip to main content
Glama
EvandroSchechtel

WhatsApp Business MCP Server

by EvandroSchechtel
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

mark_message_read

Mark WhatsApp messages as read to update conversation status and confirm message delivery using message IDs from webhooks.

Instructions

Mark a received message as read (blue checkmarks). Use the message_id from a received webhook.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
message_idYesThe wamid of the message to mark as read

Implementation Reference

  • src/whatsapp-client.ts:200-205 (handler)
    The actual implementation of the markMessageRead method that communicates with the WhatsApp API.
    async markMessageRead(messageId: string) {
  return this.request(`/${this.config.phoneNumberId}/messages`, "POST", {
    messaging_product: "whatsapp",
    status: "read",
    message_id: messageId,
  });
  • src/index.ts:270-280 (registration)
    MCP tool registration for mark_message_read, including its schema and execution hook.
    server.tool(
  "mark_message_read",
  "Mark a received message as read (blue checkmarks). Use the message_id from a received webhook.",
  {
    message_id: z.string().describe("The wamid of the message to mark as read"),
  },
  async ({ message_id }) =>
    executeWithHooks("mark_message_read", { message_id }, config, () =>
      wa.markMessageRead(message_id)
    )
);

Tool Definition Quality

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool marks messages as read, implying a mutation operation, but doesn't disclose behavioral traits like required permissions, side effects (e.g., notifications), rate limits, or error conditions. The mention of 'blue checkmarks' adds minor context about visual feedback.

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 two sentences with zero waste: the first states the purpose and visual outcome, the second provides usage guidance. It's appropriately sized and front-loaded, with every sentence earning its place.

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?

Given no annotations, no output schema, and a simple single-parameter tool, the description is adequate but incomplete. It covers the basic purpose and usage hint but lacks details on behavioral aspects like permissions or error handling, which are important for a mutation tool. The context signals indicate low complexity, so this is minimally viable.

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 the parameter 'message_id' fully documented in the schema as 'The wamid of the message to mark as read.' The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Mark a received message as read') and the resource ('message'), with specific visual feedback ('blue checkmarks'). It distinguishes from siblings by focusing on read status updates rather than sending messages or managing templates, though it doesn't explicitly contrast with other tools.

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 description provides implied usage context by specifying 'Use the message_id from a received webhook,' which suggests this tool is for processing incoming messages. However, it doesn't explicitly state when to use it versus alternatives or mention any prerequisites beyond having a message_id.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EvandroSchechtel/mcp-whatsapp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server