Skip to main content
Glama

manage_whatsapp_campaign_contacts

Universal WhatsApp campaign contacts management tool that handles all campaign recipient operations through action-based parameters. Supports add, remove, and search operations for campaign recipients: phone numbers and groups. Essential for WhatsApp campaign recipient management.

add keeps the recipients already on the campaign. On a campaign that sends a template (WhatsApp Cloud API numbers), give every variable its component exactly as on manage_whatsapp_campaigns create: body, header, header_location, button_url_N or button_copy_code_N, with N the buttonIndex that list_whatsapp_templates reports. Such a campaign only reaches phone numbers, not groups. On a campaign from a number linked by QR, each variable key fills the {{ key }} placeholder of the campaign message.

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by contact type (for search action)
pageNoResults page number (for search action)
sizeNoResults page size (for search action)
widsNoWhatsApp message IDs to remove (for remove action)
actionYesAction to perform on campaign contacts
groupsNoGroup IDs to remove (for remove action)
phonesNoPhone numbers to remove (for remove action)
searchNoSearch contacts by phone number, name, or group ID (for search action)
statusNoFilter by delivery status (for search action)
targetNoFilter by contact target: phone number or group WhatsApp ID (for search action)
channelsNoChannel IDs to remove (for remove action)
contactsNoContacts to add to campaign (for add action)
campaignIdYesWhatsApp campaign ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does disclose meaningful behavior beyond structure: add preserves already-attached recipients, and template campaigns (Cloud API) reach phone numbers only while QR campaigns use {{ key }} placeholders. It stays silent on remove semantics (permanence, whether removal affects already-sent messages), permissions, and side effects.

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 second paragraph is dense and front-loads the most important constraint (add is additive, template vs QR variable shapes). The opening is padded with self-referential boilerplate — 'Universal ... management tool', 'Essential for WhatsApp campaign recipient management' — which restates the name and wastes space an agent must read.

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?

For a 13-parameter tool with no annotations and no output schema, the definition covers only the add path and variable formatting. The remove action (three ID arrays) and the search action (kind, status, target, pagination) receive no description-level explanation, and the agent gets no sense of what a call returns or how large result pages behave.

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 genuinely adds meaning: it explains the component values (body, header, header_location, button_url_N, button_copy_code_N), ties N to the buttonIndex reported by list_whatsapp_templates, and contrasts template keys against QR placeholder keys. It gives no guidance on how to use the remove parameters (wids, groups, phones, channels) or the search filters.

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 names a specific resource (campaign recipients) and enumerates the supported operations (add, remove, search), which is enough for an agent to know what the tool does. It references sibling tools (manage_whatsapp_campaigns, list_whatsapp_templates) for related data, but never states how this tool differs from manage_whatsapp_campaigns for recipient work.

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?

Usage is implied through the operation list and the richer note that add appends to existing recipients and that template campaigns can only target phone numbers, not groups. However, there is no explicit when-to-use/when-not-to-use routing, and nothing tells the agent when to pick this over manage_whatsapp_campaigns or manage_whatsapp_contacts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources