Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Manage privacy settings

manage_privacy
Idempotent

Get or update WhatsApp privacy settings, controlling who sees last seen, profile photo, stories, online status, who can call or add to groups, and whether to send read receipts.

Instructions

The account's WhatsApp privacy settings: who sees its last seen, profile picture, stories and online status, who may add it to groups or call it, and whether it sends read receipts.

Actions:

  • get: Every privacy setting.

  • get_story_privacy: Who sees the account's stories: its contacts, all but some, or only some.

  • update: Change one or more settings. Each setting is one change on WhatsApp. Returns every setting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhat to do. See the list of actions in the tool description.
onlineNoWho sees it online. Optional for `update`.
callAddNoWho can call it: everyone, or only known contacts. Optional for `update`.
profileNoWho sees its profile picture. Optional for `update`.
storiesNoWho sees its stories. Optional for `update`.
groupAddNoWho can add the account to groups. Optional for `update`.
lastSeenNoWho sees its last seen. Optional for `update`.
messagesNoWho can message it. Optional for `update`.
accountIdNoThe wuapi account id of the linked number to act as (from list_accounts). Required for every action.
readReceiptsNo`none` stops sending read receipts (and seeing others'). Optional for `update`.

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 already disclose readOnly=false, idempotent=true, destructive=false, and openWorld=true. The description adds useful behavioral detail by noting that each setting is one WhatsApp change and that `update` returns every setting, though it does not discuss permissions, rate limits, or failure behavior.

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 resource scope and then structured as a compact action list. Every sentence contributes either purpose or action semantics, 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 10-parameter, three-action management tool with no output schema, the description covers the action modes, the privacy surfaces, and the return behavior for `get` and `update`. The remaining parameter details are fully supplied by the schema.

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 description coverage is 100%, so most parameter meaning is already covered. The action parameter explicitly defers to the tool description, and the description fulfills that by defining each action's behavior, adding value beyond the enum values.

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?

It states the resource precisely as WhatsApp privacy settings and enumerates the specific surfaces it controls: last seen, profile picture, stories, online status, group adds, calls, and read receipts. This distinguishes it from generic account/profile-management siblings even without naming an alternative.

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?

The action list clearly explains when to use each mode: `get` for all settings, `get_story_privacy` for story visibility, and `update` for changing one or more settings. It lacks explicit when-not guidance or named sibling alternatives, but the action selection context is strong.

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