Skip to main content
Glama
Sign In

WhatsApp Business API by Wassenger

by com.wassenger
OverviewDiscussionsAdmin

get_whatsapp_chat_by_id

Retrieve detailed information about a specific chat using its WhatsApp ID. Includes complete metadata, assignment info, and activity details.

Same as get_whatsapp_chats with action "by_id".

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": {
      "device": "<device>",
      "chat": "<chat>"
    },
    "name": "get_whatsapp_chat_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYesWhatsApp chat ID (e.g., 1234567890@c.us for phone numbers, 123456789000000000@g.us for groups, 123456789000000@newsletter for WhatsApp channels)
deviceYesWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
fieldsNoExplicit dot-path allowlist, e.g. ['id','name','contact.phone','unreadCount']. Overrides verbosity when set.
verbosityNoResponse detail level: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete chat objects (escape hatch).summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full behavioral burden. It does disclose the payload shape at a high level ('complete metadata, assignment info, and activity details') and reveals the equivalence to another endpoint, but says nothing about permissions, error behavior for an unknown/invalid chat ID, or that the default response is token-lean (that detail lives only in the schema).

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 short sentences, front-loaded with the verb and resource, and the second sentence carries real routing information rather than filler. Minimal waste, though the 'Includes complete metadata, assignment info, and activity details' clause is slightly vague and overlaps with what the response level enum already conveys.

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?

With no annotations and no output schema, the definition should do more heavy lifting for a 4-parameter tool. It covers purpose and gives a rough return-content sketch but omits failure modes (invalid ID, missing device), and does not note that the default verbosity is 'summary', which materially affects what the agent receives.

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% and the schema already explains the chat ID formats, device ID pattern, fields allowlist and verbosity enum in detail. The description adds only that the chat identifier is a WhatsApp ID, so the baseline 3 applies.

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?

States a specific verb and resource ('Retrieve detailed information about a specific chat') and names the identifier type used to address it (WhatsApp ID). The closing note maps it to get_whatsapp_chats with action 'by_id', which helps place it among siblings, though it does not distinguish it from the many other chat-getter siblings like search_whatsapp_chats_by_name or get_whatsapp_chats_by_status.

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 'Same as get_whatsapp_chats with action by_id' line is an implied routing hint, and 'using its WhatsApp ID' implies you must already have the ID. But there is no explicit statement of when to prefer search_whatsapp_chats_by_name (when you only have a name) or the filtered getters, so the agent must infer the boundary.

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

All WhatsApp Business API by Wassenger toolsInspect
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.

Resources