Skip to main content
Glama
Hermoso

Hermoso

Official

WhatsApp Business accounts and numbers

list_whatsapp_accounts
Read-onlyIdempotent

Lists the WhatsApp Business Accounts shared with your profile and their phone numbers, IDs, and quality ratings, so you can identify which account and number other WhatsApp tools can use.

Instructions

The WhatsApp Business Accounts SHARED WITH THIS PROFILE and the phone numbers registered on each — the ids every other WhatsApp tool needs, plus each number’s QUALITY RATING, which is what decides how many messages Meta will let it send. Start here. A WABA with no number cannot send anything and the reply says so: Hermoso does not register or verify numbers, that is WhatsApp Manager. A business portfolio that could not be read is REPORTED rather than dropped — an account missing from this list would read as "the brand has no WhatsApp", which is a claim about their business and not about our read. TWO ACCOUNTS CAN CARRY THE SAME DISPLAY NAME — always quote the display field or the id when naming one to a user, never the bare name. ONLY THE ACCOUNTS SHARED WITH THIS PROFILE ARE REACHABLE. One Meta login often administers WhatsApp for several businesses, so a human ticks which belong to this profile under Connectors > Meta > Manage accounts (or set_connector_accounts(provider:"meta")); nothing else here can see or touch the rest. With none ticked every WhatsApp tool refuses and names that as the way out. With exactly ONE ticked, wabaId is optional — pass it only to disambiguate. Read-only, 0 credits (WhatsApp conversations are billed by META to the business directly, never in Hermoso credits). Needs Meta connected.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety bar is covered; the description adds substantial context they cannot: 0 credits with billing handled by Meta directly, the requirement that Meta be connected, and the deliberate behavior of reporting unreadable business portfolios rather than silently dropping them (with the rationale that an omission would read as a false claim about the brand). It also warns that two accounts can share a display name, which is a real behavioral trap.

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?

The purpose and "start here" directive are front-loaded, and nearly every sentence carries non-obvious operational information. However, the sharing constraint is stated twice (first line and the ALL-CAPS "ONLY THE ACCOUNTS SHARED WITH THIS PROFILE ARE REACHABLE") and the heavy caps emphasis throughout adds visual noise without adding meaning.

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

Completeness5/5

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

With no input parameters and no output schema, the description carries the full burden and does so: it explains what comes back (ids, phone numbers, quality ratings, display names), what an empty result means, how errors surface, and what prerequisites must hold. Nothing an agent needs to call this correctly and interpret the result is missing.

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?

This tool takes zero parameters, so the baseline is 4. The description does clarify output-side identifiers (`display` field and ids) that matter for how results are cited, though the mention of an optional wabaId pertains to other WhatsApp tools rather than this one and could momentarily confuse an agent reading this definition in isolation.

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 and resource — the WhatsApp Business Accounts shared with this profile and the phone numbers on each — and explicitly says it returns the ids every other WhatsApp tool needs plus each number's quality rating. It also distinguishes itself from set_connector_accounts (which account-ticking happens there) and from WhatsApp Manager (which registers numbers), so an agent can place it in the ecosystem without opening a sibling schema.

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

Usage Guidelines5/5

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

"Start here" gives an explicit entry-point instruction, and the description covers the precondition (Meta must be connected), the failure mode (with none ticked every WhatsApp tool refuses), and the remediation path (Connectors > Meta > Manage accounts or set_connector_accounts). It even resolves the disambiguation case where only one account is ticked.

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

Deploy Server

Other Tools