Meta Cloud API MCP Server

subscribe_waba_webhook

Subscribe your app to WhatsApp Business Account webhooks for real-time event notifications. Override callback URL and verify token as needed.

Instructions

Subscribe your app to WABA webhooks. Optionally override the callback URL and verify token.

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": "subscribe_waba_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`verify_token`	No	Verify token for webhook validation (required if override_callback_uri is set)
`override_callback_uri`	No	Custom webhook callback URL (overrides app dashboard setting)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.5/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 of disclosing behavioral traits. It states the action and that parameters are optional, but does not mention side effects, reversibility, idempotency, or any prerequisites. For a state-changing subscription tool, this lack of transparency is a significant 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?

The description is a single, direct sentence with one additional clause. Every word serves a purpose—stating the action, the resource, and the optional parameters. There is no redundancy or unnecessary detail.

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?

The tool has no output schema and no annotations, so the description should explain return values or consequences. It only states the action and options, omitting any outcome or side-effect information. However, given the tool's simplicity, the description is adequate for basic understanding but lacks completeness regarding what happens after subscription.

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?

The input schema has 100% description coverage for both parameters, so the baseline is 3. The description merely repeats parameter names ('override the callback URL and verify token') without adding meaning beyond the schema. It does not highlight the conditional dependency between verify_token and override_callback_uri, but that is captured in 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 clearly states the verb 'subscribe' and resource 'WABA webhooks', making the tool's purpose specific and unambiguous. It also distinguishes from the sibling 'unsubscribe_waba_webhook' by its name and action. The mention of optional override parameters adds further clarity.

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 implies when to use the tool (when you want to subscribe to webhooks) but provides no explicit exclusions, alternatives, or prerequisites. It does not mention the sibling 'unsubscribe_waba_webhook' or clarify conditions like the conditional requirement for verify_token, leaving usage guidance implied rather than explicit.

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