MCP WhatsApp

whatsapp_update_group_participants

Update a WhatsApp group's participant list by adding or removing members using their phone numbers and the group's JID.

Instructions

Add or remove group participants. action: 'add'|'remove'. participants: phone list, no '+'.

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": {
      "group_jid": "<group_jid>",
      "participants": "<participants>"
    },
    "name": "whatsapp_update_group_participants"
  }
}

Input Schema

Name	Required	Default
`group_jid`	Yes
`participants`	Yes
`action`	No	add

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 15, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description has the full burden. It mentions the phone number format (no '+') but fails to disclose behavioral traits like required permissions, potential consequences of removal, or error conditions.

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 concise at two sentences, with the first sentence stating the purpose and the second detailing parameters. No unnecessary words, though more detail could fit without losing conciseness.

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's potential for destructive actions (removing participants), the description lacks warnings or prerequisites. It also does not explain the output schema or handle edge cases, making it incomplete for safe use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain all parameters. It partially covers 'action' and 'participants' but omits 'group_jid' entirely, leaving a required parameter unexplained.

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 verb 'Add or remove' and the resource 'group participants'. It distinguishes from sibling tools like whatsapp_create_group or whatsapp_get_group_info by focusing on participant modification.

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 when to add vs. remove participants, or prerequisites like being a group admin.

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

Deploy Server