Kopern

kopern_connect_whatsapp

Idempotent

Connect AI agents to WhatsApp Business using Meta Cloud API credentials. Enable automated messaging through WhatsApp's platform.

Instructions

Connect an agent to WhatsApp Business. Requires Meta Cloud API credentials.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>",
      "phone_number_id": "<phone_number_id>",
      "access_token": "<access_token>"
    },
    "name": "kopern_connect_whatsapp"
  }
}

Input Schema

Name	Required	Description
`agent_id`	Yes	The agent ID or name
`access_token`	Yes	WhatsApp Cloud API access token
`phone_number`	No	Display phone number (optional)
`verify_token`	No	Webhook verify token (optional)
`phone_number_id`	Yes	WhatsApp phone number ID (from Meta dashboard)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.5Apr 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations provide idempotentHint=true and readOnlyHint=false, so some behavioral context is already given. The description adds the credential requirement but does not disclose details such as whether an existing connection is overwritten, side effects like webhook setup, or what the return value indicates. Some value beyond annotations, but limited.

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?

Two sentences, front-loaded with the primary action, and no redundant information. Every word earns its place.

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?

Given the low complexity and full parameter descriptions, the tool is fairly complete. The idempotency annotation adds a useful safety signal. However, it lacks any mention of effects (e.g., notifications, webhook setup) or return values, which could matter for an integration tool. Still, for a simple connector, this is adequate.

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 descriptions cover 100% of parameters, so the baseline is 3. The description mentions credentials, which loosely aligns with access_token and phone_number_id, but does not offer any additional parameter-level meaning beyond the schema.

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?

The description states a specific verb 'Connect' and a clear resource 'agent to WhatsApp Business', distinguishing it from sibling connect tools like Slack or Telegram. The purpose is immediately obvious.

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?

The description clearly implies use for WhatsApp connectivity, but does not explicitly state when to choose this tool over alternatives like other connect tools. It mentions a prerequisite (Meta Cloud API credentials) but lacks comparative guidance.

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