wwebjs-mcp

client_syncHistory

Sync WhatsApp chat history for a session. Provide session ID and optionally chat ID to retrieve past messages.

Instructions

[Client] Sync chat history

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_syncHistory"
  }
}

Input Schema

Name	Required	Description	Default
`chatId`	No	ID of the chat
`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

D1.9/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It offers no information about side effects, permissions, whether this reads or modifies data, or what the sync operation does. 'Sync' is vague and could imply a range of behaviors, but the description adds no transparency beyond the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (three words), but this is under-specification rather than effective conciseness. It omits essential information and does not front-load any useful detail. Like the 'Process' example, it fails to earn its place as a helpful description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is grossly inadequate for a tool with two parameters, no output schema, and no annotations. It does not explain the purpose, usage, or behavior. The sibling 'chat_syncHistory' and other related tools remain indistinguishable, leaving the agent without essential context.

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?

The input schema has 100% parameter descriptions, so the schema covers the parameters adequately. The tool description adds no additional meaning about parameters, but the baseline is 3 because the schema does the heavy lifting.

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

Purpose2/5

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

The description 'Sync chat history' merely restates the tool name 'client_syncHistory' without providing a specific verb or clarifying what syncing entails. It fails to distinguish this tool from the sibling 'chat_syncHistory', leaving ambiguity about the scope and function. This is closer to a tautology than a clear purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. There is no mention of prerequisites, scenarios, or comparisons with siblings like 'client_getChats' or 'chat_fetchMessages'. The description provides no usage context whatsoever.

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

Deploy Server