wwebjs-mcp

client_getChatsByLabelId

Fetches all chats associated with a given label ID in a WhatsApp session, enabling targeted retrieval of labeled conversations.

Instructions

[Client] Get all chats for a specific label

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": {
      "sessionId": "<sessionId>"
    },
    "name": "client_getChatsByLabelId"
  }
}

Input Schema

Name	Required	Description	Default
`labelId`	No	ID of the label
`sessionId`	Yes	Unique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description does not add behavioral context beyond the basic operation. It fails to disclose whether the label must exist, what happens when labelId is omitted (schema marks it optional), or whether pagination is involved. The description merely restates the function without deeper insight into side effects or edge cases.

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 a single concise phrase with no wasted words. It is front-loaded with the verb 'Get' and the resource 'chats', making it easy to parse and understand immediately.

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 the simple nature of the tool (two parameters, no output schema), the description covers the core purpose adequately. However, the optional labelId creates ambiguity, and the lack of any return value or error behavior explanation leaves gaps for an agent. The description is minimally viable but not comprehensive.

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% with descriptions for both labelId and sessionId, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides, such as format details or relationships between parameters.

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 'Get all chats for a specific label' with a specific verb and resource, distinguishing it from sibling tools like client_getChats (all chats) and client_getChatById (single chat). The phrase 'specific label' adds scope, making the purpose unambiguous.

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 implies usage when a label ID is available, but it does not explicitly mention alternatives or conditions for when to use this tool versus client_getChats or client_getChatLabels. No exclusions or prerequisites are stated, leaving usage guidance to inference.

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

Deploy Server