Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Change a group's info and settings

manage_group_settings
DestructiveIdempotent

Change a group's name, description, who can send or edit info, join approval, member-add rules, and picture, or remove its picture, via a wuapi account.

Instructions

Change a group the account administers: its name, description and settings (who can send, who can edit the info, whether joining needs approval, who can add members), and its picture.

Actions:

  • update: Change any of name, description, announce, locked, joinApproval and memberAddMode. Returns the group.

  • set_picture: Set the group picture from an https URL or base64 JPEG. Returns the picture.

  • delete_picture: Remove the group picture. Needs confirm: true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoThe group name. Optional for `update`.
actionYesWhat to do. See the list of actions in the tool description.
lockedNo`true`: only admins can edit the group info. Optional for `update`.
confirmNoMust be true. The group picture is removed. Only set it after the user asked for this or agreed to it. Required for `delete_picture`.
groupIdNoThe group id (`...@g.us`), from list_groups. Required for every action.
announceNo`true`: only admins can send messages. Optional for `update`.
accountIdNoThe wuapi account id of the linked number to act as (from list_accounts). Required for every action.
pictureUrlNoThe picture as a public https URL of a JPEG. wuapi downloads it. Pass this or `pictureBase64`. Optional for `set_picture`.
descriptionNoThe group description. An empty string clears it. Optional for `update`.
joinApprovalNo`true`: new members need an admin's approval (see manage_group_joins). Optional for `update`.
memberAddModeNoWho can add members. Optional for `update`.
pictureBase64NoThe picture as a base64 JPEG. Pass this or `pictureUrl`. Optional for `set_picture`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive and idempotent behavior, but the description adds substantial operational detail: delete_picture removes the picture and needs confirm: true only after user consent; update returns the group; set_picture returns the picture; and set_picture downloads the image from an https URL.

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 front-loaded with the tool's overall purpose, then uses a concise bulleted action list to separate the three operations. Every sentence carries relevant information with no filler.

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

Completeness5/5

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

For a 12-parameter, multi-action, destructive tool, the description covers the actions, their required conditions, return values, and input constraints. With the schema and annotations carrying safety and parameter details, nothing critical is missing.

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 12 parameters individually. The description adds useful action-level grouping of fields but does not introduce much semantic detail beyond what the schema already provides.

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 states a specific verb and resource: change a group's name, description, settings, and picture, with three explicit actions. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as manage_group_joins or manage_group_participants beyond a passing reference.

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?

Each action is given clear context: update lists which fields can change, set_picture explains the two image input forms, and delete_picture requires confirm: true and says to use it only after the user asked. It lacks explicit when-not guidance and does not fully clarify the boundary with manage_group_joins.

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