Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage communities

manage_community

Create and manage WhatsApp communities, link or unlink groups, and list community groups and members.

Instructions

WhatsApp communities: a community is a group with community: true that links other groups. Create one, list its groups and members, and link or unlink groups (the account must admin both). get_group reads the community itself; send to it like a group. To create a new group inside a community, use create_group with communityId; list_groups shows each group's communityId.

Actions:

  • create: Create a community with the account as owner. Returns it.

  • list_groups: The groups linked to the community, marking its default (announcement) group.

  • list_members: Members across the community's linked groups.

  • link_group: Link a group into the community.

  • unlink_group: Unlink a group from the community. The group itself stays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe community name. Required for `create`.
limitNoPage size, 1 to 100. Default 20. Optional for `list_groups`, `list_members`.
actionYesWhat to do. See the list of actions in the tool description.
cursorNo`nextCursor` from the previous page, to get the next one. Optional for `list_groups`, `list_members`.
groupIdNoThe group to link or unlink (`...@g.us`). Required for `link_group`, `unlink_group`.
accountIdNoThe wuapi account id of the linked number to act as (from list_accounts). Required for every action.
communityIdNoThe community's group id (`...@g.us`), from list_groups (`community: true`). Required for `list_groups`, `list_members`, `link_group`, `unlink_group`.
idempotencyKeyNoOptional. Reuse the same key when retrying this exact call: within 24 hours wuapi returns the first result instead of doing it twice. Optional for `create`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the bar is lower, yet the description adds real behavioral context: create returns the community, unlink leaves the group intact, and admin rights are required for linking. It does not detail error modes or pagination behavior beyond the schema.

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 concept explanation is front-loaded before the action list, and each bullet earns its place. Slightly longer than strictly necessary for a single-tool definition, but no filler sentences.

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?

Covers a five-action mutation tool with no output schema: it explains return shape for create, list semantics, and the persistence guarantee for unlink. Missing only edge-case behavior (what happens to linked groups when a community is deleted), which is minor.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-cutting semantics the schema cannot: which params each action needs (name for create, groupId for link/unlink, communityId for the rest) and where communityId comes from.

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 set and resource: creating, listing, linking, unlinking WhatsApp community groups, with each action enumerated and defined. It explicitly distinguishes itself from siblings by naming get_group and create_group and their respective roles.

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

Usage Guidelines5/5

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

Routes the agent explicitly: use get_group to read a community, use create_group with `communityId` to make a nested group, list_groups reveals `communityId`. It also states the precondition that the account must admin both groups for link/unlink.

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