Skip to main content
Glama

manage_whatsapp_contacts

Comprehensive WhatsApp contacts management with action-based operations. Supports listing, searching, creating, updating, deleting contacts, bulk operations, and metadata management. All contact operations including CRUD, filtering, pagination, and metadata handling in one unified tool.

Input Schema

NameRequiredDescriptionDefault
crmNoCRM system name (for create, update actions)
widNoFilter contacts by WhatsApp IDs (for list action)
cityNoContact city (for create, update actions)
kindNoContact category (for create, update actions)
nameNoContact first name (for create, update actions)
pageNoPage number for pagination (0-based, for list action)
sortNoSort field and order (e.g., "-createdAt", "name", for list action)
typeNoFilter contacts by type (for list action)
afterNoFilter contacts created after this date (for list action)
emailNoContact email address (for create, update actions)
limitNoNumber of contacts to retrieve (max 200, for list action)
notesNoPrivate notes about the contact (for create, update actions)
ownerNoFilter contacts assigned to specific agents (for list action)
phoneNoPhone number for create action, or array of phone numbers for list filtering
titleNoContact title (Mr., Mrs., Dr., etc., for create, update actions)
actionYesAction to perform on WhatsApp contacts
assignNoAssign contact to specific agent (for create action)
beforeNoFilter contacts created before this date (for list action)
crmRefNoCRM reference ID or URL (for create, update actions)
deviceYesWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
fieldsNoExplicit dot-path allowlist, e.g. ['wid','phone','info.email']. Overrides verbosity when set.
genderNoContact gender (for create, update actions)
searchNoSearch contacts by name, surname, phone, email, company, address, or notes (for list action)
statusNoFilter contacts by status (for list action)
upsertNoUpdate the contact if it already exists instead of failing with 409 (for create and bulk_create actions)
addressNoContact address (for create, update actions)
countryNoContact country 2-letter ISO code (for create, update actions)
includeNoInclude related entities in response
surnameNoContact surname/last name (for create, update actions)
altPhoneNoAlternative phone number (for create, update actions)
birthdayNoContact birthday in YYYY-MM-DD format (for create, update actions)
contactsNoArray of contacts to create (max 1000, for bulk_create action)
currencyNoContact currency 3-letter ISO code (for create, update actions)
metadataNoContact metadata key-value pairs (for create, update, update_metadata, upsert_metadata actions)
timezoneNoContact timezone (for create, update actions)
verbosityNoResponse detail level for list/get: summary = curated high-signal fields (default, token-lean); standard = broader set; full = complete contact objects (escape hatch).summary
contactWidNoWhatsApp contact ID (required for get, update, delete, update_metadata, upsert_metadata actions)
postalCodeNoContact postal code (for create, update actions)
companyCodeNoCompany code (for create, update actions)
companyNameNoCompany name (for create, update actions)
companyRoleNoContact role in company (for create, update actions)
descriptionNoContact description (for create, update actions)
metadataKeyNoFilter contacts with specific metadata keys (for list action)
companyEmailNoCompany email (for create, update actions)
companyPhoneNoCompany phone number (for create, update actions)
companyTaxIdNoCompany tax ID (for create, update actions)
removeFieldsNoFields to remove/clear from contact (for update action)
updatedAfterNoFilter contacts updated after this date (for list action)
metadataValueNoFilter contacts with specific metadata values (for list action)
updatedBeforeNoFilter contacts updated before this date (for list action)
companyCountryNoCompany country 2-letter ISO code (for create, update actions)
companyWebsiteNoCompany website (for create, update actions)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and largely fails it: it does not disclose that 'delete' is destructive/irreversible, that 'upsert' suppresses 409 conflicts, that bulk_create caps at 1000 items, or what permissions/auth are needed. Only vague hints ('bulk operations', 'pagination') appear, leaving the risk profile of a mutation-heavy tool undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The three clauses are largely redundant, repeating 'all contact operations/CRUD/filtering/metadata' from different angles without adding information. The filler opener 'Comprehensive ... with action-based operations' and the restatement in the final sentence waste space that could have been spent on action-specific guidance.

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

Completeness2/5

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

For a 52-parameter, 8-action mutation tool with no annotations and no output schema, the description is far too thin: it omits action-specific requirements, destructive-operation warnings, bulk limits, and response behavior. An agent still relies almost entirely on the schema and must guess at risk and routing.

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 every one of the 52 parameters is documented inline (including action-gating notes like 'for create, update actions'), which sets the baseline at 3. The description itself adds no parameter meaning beyond the schema and merely gestures at 'metadata handling' and 'filtering' without elaborating.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (WhatsApp contacts) and lists operations (list, search, create, update, delete, bulk, metadata), so the general purpose is inferable. However, it never differentiates itself from the very similarly named sibling manage_whatsapp_contact_actions, nor does it clarify the boundary against manage_whatsapp_campaign_contacts, so an agent cannot confidently route between these overlapping tools from the text alone.

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?

There is no when-to-use guidance, no mention of which tool to prefer for contact actions, and no statement of prerequisites (e.g., needing a valid device ID, or when to choose this over manage_whatsapp_contact_actions). The action list is enumerated but the conditions that select each action are not described at all.

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