wwebjs-mcp

groupChat_leave

Leave a WhatsApp group by providing the session ID and chat ID. This exits the group, stopping messages and updates from that conversation.

Instructions

[Group Chat] Leave the group

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": "groupChat_leave"
  }
}

Input Schema

Name	Required	Description	Default
`chatId`	No	Unique WhatsApp id for the given chat group
`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

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral consequences. It only says 'Leave the group' without mentioning whether the action is reversible, requires admin rights, or affects the user's membership status. The behavioral impact is unclear, leaving the agent to guess the tool's side effects.

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?

The description is extremely concise and front-loaded, containing no filler words. It quickly communicates the primary action. However, it is so brief that it borders on under-specification, though for this simple operation it still counts as efficient rather than wasteful.

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?

The tool is simple but lacks critical context: prerequisites (must be a current group member), whether the action is reversible, and any side effects on chat history or the session. With no output schema and no annotations, the description fails to provide a complete picture for an agent to confidently invoke it.

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%, as both chatId and sessionId have descriptive text in the input schema. The description adds no additional parameter meaning, but per the rubric, a high coverage baseline of 3 is appropriate. The parameters are already well-documented in the schema.

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 'Leave the group' clearly states a specific action (leave) on a specific resource (group). The '[Group Chat]' prefix contextualizes it within the group chat domain. Among the many sibling tools, no other tool explicitly covers leaving a group, so it is well distinguished.

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 information about when to use this tool versus alternatives. For example, it does not clarify that this is for the current user leaving a group, as opposed to groupChat_removeParticipants which removes other participants, or chat_delete which removes the chat locally. No exclusions or alternative references are given.

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

Deploy Server