Skip to main content
Glama
Sign In
wuapi MCP server

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Make participants admins

promote_group_participants
Idempotent

Promote selected contacts to group admins by providing group ID, account ID, and contact IDs.

Instructions

Make participants admins of a group the account administers.

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": {
      "accountId": "<accountId>",
      "groupId": "<groupId>",
      "contactIds": "<contactIds>"
    },
    "name": "promote_group_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupIdYesThe group id (`...@g.us`), from list_groups.
accountIdYesThe wuapi account id of the linked number to act as (from list_accounts).
contactIdsYesContact ids: E.164 with + (`+584241112233`) or `lid:<digits>`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already cover readOnlyHint=false, idempotentHint=true, and openWorldHint=true. The description adds no behavioral context beyond the action itself, such as reversible effects, permission requirements, or consequences for already-admin participants. It simply restates the purpose without enriching the agent's understanding of side effects or environment impact.

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, tightly worded sentence that states the core action and a scope qualifier. There is no filler or repetition; it is optimally concise and immediately communicates the tool's purpose.

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

Completeness3/5

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

The description is sufficient for a straightforward mutation tool with all parameters documented in the schema and annotations covering safety and idempotency. However, it lacks any explanation of the effect on existing admins or the behavior when promoting multiple contacts, and with no output schema, the return value is unstated. It is minimally complete but not rich.

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 baseline is 3. The description does not add parameter-specific details beyond what the schema already provides. It does not elaborate on contactIds format or groupId constraints, which are already well-documented in the schema, so no extra semantic value is added.

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 action: 'Make participants admins' of a group, which is a specific verb+resource. It implicitly distinguishes from sibling tools like add_group_participants and demote_group_participants by the promotion action, though it doesn't name them explicitly. The constraint 'the account administers' adds scope clarity.

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. It does not mention that demote_group_participants is the inverse operation, nor does it offer context on when promotion is appropriate. The only hint is the account-administers constraint, but no exclusions or alternative-condition guidance is given.

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

Deploy Server

Other Tools