Skip to main content
Glama

Link to connect WhatsApp

whatsapp_connect_link
Read-onlyIdempotent

The portal page where an owner or admin connects this business's WhatsApp Business account. Connecting goes through Meta's own sign-up window in the browser, so it happens on that page, not in the chat. Returns a link only; changes nothing.

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_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds context beyond the annotations by naming the required role (owner or admin) and explaining that the actual connection happens in Meta's own browser window rather than through the API. 'Returns a link only; changes nothing' restates readOnlyHint/destructiveHint=false, so it is reinforcement rather than new information, and nothing is said about link expiry or reuse.

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?

Three short sentences, each doing distinct work: what the page is, why it must be a browser step, and what the tool itself returns. The key constraint (link only, no mutation) is front-loaded and unambiguous.

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

Completeness4/5

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

For a zero-parameter, no-output-schema tool, the description covers who can use it, what it returns, and where the real work happens. The only gap is the nature of the returned link itself — format, lifetime, or whether it is single-use — which an agent cannot infer from anything supplied.

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?

Zero parameters, so there is nothing for the description to compensate for; baseline applies. The description correctly signals a no-input tool by describing it purely in terms of what it returns.

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?

Names a specific resource (the portal page for connecting this business's WhatsApp Business account) and states the output precisely: 'Returns a link only.' It contrasts with in-chat actions ('that page, not in the chat'), which implicitly separates it from the whatsapp_send_* siblings, though it never names one.

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?

Implies usage through the flow description — the connect step happens in Meta's sign-up window in the browser, so hand the link to an owner or admin — but offers no explicit when-to-use trigger or named alternative. An agent must infer that this is the prerequisite step before any WhatsApp sending tool.

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.