wwebjs-mcp

groupChat_promoteParticipants

Promote group chat members to admin by passing participant IDs, chat ID, and session ID. Grant admin privileges in WhatsApp groups.

Instructions

[Group Chat] Promote the participants. Promote participants by ID to admins

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

Input Schema

Name	Required	Description
`chatId`	No	Unique WhatsApp id for the given chat group
`sessionId`	Yes	Unique identifier for the session (alphanumeric and - allowed)
`participantIds`	No	Unique WhatsApp identifiers for the participants

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?

No annotations are provided, so the description carries the full burden. It only states the action without mentioning permissions, reversibility, or side effects. For a mutation tool, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but contains redundancy: 'Promote the participants.' and 'Promote participants by ID to admins' say essentially the same thing. Could be streamlined to one sentence.

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 a mutation with no annotations and no output schema. The description covers the core function, but lacks behavioral context such as when to use, requirements, or potential effects. While parameters are well-documented in the schema, the overall context is incomplete for an agent to fully understand invocation.

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 covers all three parameters with descriptions. The description adds minimal value by saying 'by ID' but this is already explicit in the schema. Baseline 3.

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 (promote participants) and the resource (group chat). It distinguishes from sibling tools like groupChat_demoteParticipants by explicitly mentioning 'promote' to admins.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like demote or add participants. The usage is implied by the description, but there is no mention of prerequisites (e.g., being an admin) or exclusionary context.

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

Deploy Server