wwebjs-mcp

client_unpinChat

Unpin a chat in WhatsApp Web by providing the session ID and chat ID, so the chat is removed from the pinned list.

Instructions

[Client] Unpin the chat

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

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

C2.8/5.0

Behavior2/5

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

There are no annotations, so the description must fully disclose behavioral traits. It only says 'Unpin the chat' without mentioning side effects, error conditions, idempotency, or any requirements. This leaves the agent unaware of important operational behavior.

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

Conciseness3/5

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

The description is very concise (one short sentence) with no wasted words, but it is under-specified. While it is front-loaded, it lacks substance to fully inform the agent, making it not ideally sized.

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

Completeness2/5

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

Given it's a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain prerequisites (e.g., chat must be pinned), behavior if already unpinned, or any session requirements. The simple schema doesn't compensate for the absence of operational 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?

Schema description coverage is 100% with both chatId and sessionId described with examples. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 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?

The description clearly states the action 'Unpin the chat' with a specific verb and resource, making the core purpose understandable. However, it doesn't explicitly differentiate from sibling tools like client_pinChat or other chat actions beyond the verb itself.

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?

The description provides no guidance on when to use this tool vs alternatives (e.g., client_pinChat), nor any context about prerequisites like whether the chat must already be pinned. It simply states the action without usage context or exclusions.

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

Deploy Server