Skip to main content
Glama
WhatsApp MCP Server

WhatsApp MCP Server

get_chat

Retrieve detailed metadata for a WhatsApp chat by JID, phone number, or contact name, including unread and message counts, group members, and media breakdowns.

Instructions

Retrieve detailed metadata for a WhatsApp chat session by JID, phone number, or contact name. Includes unread count, message count, group membership roster (for group chats), and media breakdowns.

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_id": "<chat_id>"
    },
    "name": "get_chat"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesWhatsApp JID (e.g. 1234567890@s.whatsapp.net or group@g.us), phone number, or contact name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose the returned data shape and that roster data is conditional on group chats, but says nothing about behavior for unknown identifiers, permissions/auth requirements, or whether the lookup is read-only and side-effect free.

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?

Two tight sentences with the core action front-loaded and the payoff (returned fields) immediately after. Every clause carries information; only a small amount of space is spent restating identifier formats already in the schema.

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?

With no output schema, the description usefully enumerates what comes back, and for a single-parameter read tool that is most of what an agent needs. Missing are error/not-found behavior and any hint about permissions, which are the remaining gaps for a tool with zero annotation coverage.

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 the single chat_id parameter is fully documented in the schema, so baseline is 3. The description's mention of 'JID, phone number, or contact name' largely restates the schema's identifier list rather than adding resolution order or fallback behavior.

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 names a specific verb ('Retrieve') and resource ('detailed metadata for a WhatsApp chat session') and enumerates the returned fields (unread count, message count, roster, media breakdown). It does not explicitly distinguish itself from siblings like list_chats or get_message_context, which keeps it below a 5.

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?

Usage is only implied: fetch details for one specific chat. There is no guidance on when to prefer this over list_chats (to discover chats) or get_message_context, and no stated prerequisites such as needing an existing/known chat identifier.

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