WhatsMCP: MCP for WhatsApp

Create Group

wa_create_group

Create a WhatsApp group with a name and initial members from one of your accounts. Returns the new group's JID (use it as wa_send_message's 'to') and an invite link.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	the group name (max 25 characters)
`members`	No	initial members — phone numbers (E.164) or JIDs, comma- or space-separated; do NOT include your own number
`account_id`	Yes	the account to create the group from, as returned by wa_list_accounts

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No	the rows of a list operation
`status`	Yes	ok (the operation succeeded) or refused (see refusal; for wa_update_group, applied lists the changes that took effect before it)
`applied`	No	wa_update_group only: the settings that were changed, in order — on a refusal, the ones that took effect before it
`refusal`	No	present only when status is refused
`summary`	No	a human-readable result
`group_jid`	No	the new group's JID (wa_create_group only) — use it as wa_send_message's 'to'
`invite_link`	No	the group's invite link (wa_create_group or wa_get_group_invite_link)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 22, 2026

addedOutput schema / properties / applied

Added value: +{
+  "description": "wa_update_group only: the settings that were changed, in order — on a refusal, the ones that took effect before it",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

changedOutput schema / properties / status / description

Previous value: -"ok (the operation succeeded) or refused (nothing was done)"New value: +"ok (the operation succeeded) or refused (see refusal; for wa_update_group, applied lists the changes that took effect before it)"

First observedSep 17, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations are present (all false) so the description carries a lighter burden; it adds the non-obvious facts that group creation is side-effecting and returns both a JID and an invite link. It does not contradict the annotations, though it could further disclose that members are optional or mention any creation limits. Core behavioral context is provided.

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?

Two sentences with no filler: the first states the action and scope, the second states the return value and its downstream use. Essential information is front-loaded and every clause earns its place.

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

Completeness4/5

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

For a 3-parameter tool with a full output schema and annotations, the description covers purpose, return value, and downstream usage. The only gap is that 'with a name and initial members' could imply members are required, whereas the schema marks it optional, though the schema itself resolves this ambiguity.

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%, so the schema already documents all three parameters in detail. The description only restates the concepts of name, initial members, and accounts without adding format, constraints, or examples beyond the schema. Baseline 3 applies.

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?

States a specific verb ('Create'), resource ('WhatsApp group'), and scope ('from one of your accounts'). It also specifies the return value (JID and invite link), and the JID is explicitly tied to wa_send_message, which distinguishes it from siblings like wa_update_group, wa_delete_group, and wa_join_group.

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

Usage Guidelines4/5

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

Gives clear context for when to use the tool: creating a new WhatsApp group with a name and initial members. It also provides a downstream usage pointer by telling the agent to use the returned JID as wa_send_message's 'to'. It does not explicitly name alternatives or exclusions, but the create-vs-modify distinction is unambiguous within the sibling set.

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

All WhatsMCP: MCP for WhatsApp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?