wwebjs-mcp

client_createGroup

Create a new WhatsApp group on an active session by specifying a title and list of contact IDs to add as participants.

Instructions

[Client] Create a new 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": "client_createGroup"
  }
}

Input Schema

Name	Required	Description
`title`	No	Group title
`options`	No	An object that handles options for group creation
`sessionId`	Yes	Unique identifier for the session (alphanumeric and - allowed)
`participants`	No	A single contact ID as a string or an array of contact IDs to add to the group

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'Create a new group' without explaining side effects, permissions, response format, or how it interacts with the session. This is insufficient for an agent to anticipate the tool's behavior.

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 a single, short sentence that is immediately clear and contains no filler. However, it is so terse that it may not add enough value beyond the tool name, slightly reducing its effectiveness.

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 the tool has four parameters, a nested object (options), and no annotations or output schema, the description is under-specified. It does not explain what the tool returns, prerequisites, or how to use the parameters, leaving important gaps for an agent.

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 covers all four parameters with examples and descriptions, so the baseline is 3. The description adds no additional meaning to the parameters, merely restating the tool's purpose.

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 uses a specific verb ('Create') and resource ('a new group'), clearly indicating the tool's function. However, it does not differentiate this from other group-related sibling tools like groupChat_addParticipants or groupChat_setSubject, leaving ambiguity about its exact scope.

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 versus alternatives such as groupChat_* tools. It does not mention requirements like an active session or that this is the correct tool for creating groups as opposed to modifying them.

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

Deploy Server