Meta Cloud API MCP Server

get_waba_account

Retrieve WhatsApp Business Account information: name, status, health, verification, and messaging limits to monitor account health and compliance.

Instructions

Get WhatsApp Business Account information — name, status, health, verification, messaging limits

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

Input Schema

Name	Required	Description	Default
`fields`	No	Specific WABA account fields to retrieve

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries full responsibility. It discloses the type of information returned, but does not mention the optional fields parameter or the default behavior when it's omitted. The read-only nature is implied by 'Get' but not explicitly stated.

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?

A single, concise sentence that front-loads the core action and enumerates the key information categories without waste.

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 is simple with one optional parameter, but the description omits that details can be customized via the fields parameter and what happens if omitted. The absence of an output schema makes this a gap, though the listed attributes provide some expectation.

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 schema already covers the fields parameter with 100% coverage and a detailed enumeration. The description lists some fields but doesn't add additional semantics like default behavior or formatting.

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 uses the verb 'Get' with a specific resource 'WhatsApp Business Account information' and lists key attributes (name, status, health, verification, messaging limits). This clearly distinguishes it from sibling tools for templates, flows, messages, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context is clear that this tool is for retrieving WABA account details, and sibling tools cover different resources. However, it doesn't explicitly mention when to use this over alternatives or any exclusions.

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