wwebjs-mcp

client_createChannel

Create a new WhatsApp channel for an existing session by providing a title and optional description.

Instructions

[Client] Create a new channel

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

Input Schema

Name	Required	Description
`title`	No	The title of the channel
`options`	No
`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.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits beyond the obvious 'create' action. It fails to mention that a valid sessionId is required, whether the operation is destructive or reversible, or what the response/return value will be. The agent cannot anticipate side effects, making this a significant gap.

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, front-loaded sentence that conveys the core purpose without unnecessary words. It is appropriately concise for a tool with only three parameters, and there is no redundancy or filler.

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 has no output schema and no annotations, so the description must supply context about prerequisites, return values, and side effects. It does none of these. The description is too minimal to support correct invocation in edge cases (e.g., invalid session, duplicate channel name, or success/failure indicators).

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 schema already describes title and sessionId, covering 67% of top-level parameters, which mitigates the lack of parameter info in the description. However, the 'options' wrapper is not explained, and the description adds no clarification about how parameters relate to the operation. This is a moderate score: schema covers most, but the description doesn't add meaning.

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 the action ('Create') and resource ('a new channel'), which is specific and unambiguous. It distinguishes from sibling tools like client_createGroup or channel_setSubject by the resource type. The '[Client]' prefix indicates the tool operates at the client level, adding useful context.

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 client_createGroup or channel_setSubject. There is no mention of prerequisites (e.g., an active session), excluded scenarios, or why one would choose this over other channel-related tools. The agent is left without decision support.

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

Deploy Server