Skip to main content
Glama

List WhatsApp Business Accounts owned by a Business

wa_business_owned_wabas

Retrieve all WhatsApp Business Accounts (WABAs) owned by a specified business ID, enabling access to account data for management and integration.

Instructions

GET /{business_id}/owned_whatsapp_business_accounts — returns WABAs owned by the parent Business. Find business_id via Business Manager or /me/businesses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
business_idYes
fieldsNo
limitNo
Behavior2/5

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

No annotations exist, so description bears full burden. It only states it returns WABAs but omits traits like read-only nature, required permissions, error handling, or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, efficient and front-loaded with the main action. Could be improved by adding parameter descriptions.

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

Completeness2/5

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

Given no output schema and 3 parameters, the description lacks essential context: no mention of return format, pagination, field selection, or default limit behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and description only mentions business_id. No explanation for fields array or limit parameter, leaving the agent uninformed about their semantics.

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?

Description clearly states HTTP GET method, resource path, and that it returns WABAs owned by the parent Business. Distinguishes from siblings like wa_phone_numbers and wa_analytics by focusing on owned accounts.

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?

Hints at finding business_id via Business Manager or /me/businesses, which is helpful. However, no explicit guidance on when to use this vs alternative WhatsApp tools or exclusion conditions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nourpups/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server