Skip to main content
Glama

WhatsApp: Connect

whatsapp_connect
Destructive

Connect or reconnect the user's WhatsApp account directly in the conversation without leaving the agent. Default mode returns a QR code image to scan from WhatsApp > Linked devices; with phone_number it returns a pairing code to type on the phone instead (useful when the QR image cannot be displayed). Then poll account_connection_status until connected. Requires an active trial/subscription and a free WhatsApp slot on the plan; otherwise the result explains the upgrade. Use account_id to re-authenticate an existing disconnected WhatsApp account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "whatsapp_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoNilyo connection ID (unipile_account_id from list_connected_accounts) of an EXISTING account to re-authenticate. Omit to connect a new account.
phone_numberNoOptional. International phone number of the WhatsApp account, digits only (e.g. 33612345678). When provided, a pairing code is returned instead of a QR code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: prerequisites (active trial/subscription, free WhatsApp slot), what happens when they are unmet ('the result explains the upgrade'), and the required polling loop. It does not explain the destructiveHint=true annotation (what state is created or replaced on reconnect), which is the notable remaining gap.

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?

Four tight sentences, front-loaded with the primary action, then mode selection, then the mandatory follow-up, then prerequisites and the re-auth variant. No filler or repetition.

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 zero-required-parameter connect tool with no output schema, the description covers mode selection, the post-call polling requirement, eligibility gating, and the failure message shape. An agent has everything needed to call it correctly and know what to do next.

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 baseline is 3; the description earns an extra point by framing the two parameters as mutually exclusive modes (QR vs pairing code) and by tying account_id to the re-authentication use case rather than merely restating the field definitions.

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 and resource ('Connect or reconnect the user's WhatsApp account') and immediately distinguishes the two operational modes (QR vs pairing code) plus the re-auth path via account_id. An agent can tell it apart from account_connect, telegram_connect and whatsapp_send_message without opening a schema.

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?

Gives explicit selection logic: default returns a QR image, phone_number switches to a pairing code 'when the QR image cannot be displayed', and account_id is for re-authenticating an existing disconnected account. It also names the follow-up step ('poll account_connection_status until connected') and the gating conditions (trial/subscription, free slot).

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.