Radar noEixo

List whatsapp templates

list_whatsapp_templates

Read-only

📱 TEMPLATES WABA — Lista os templates de mensagem do WhatsApp Business da conta (WABA), com status de aprovação da Meta (APPROVED, PENDING, REJECTED, PAUSED). Use antes de disparar cadência/automação com envio FRIO de WhatsApp (sem janela de atendimento aberta), que exige um template já APPROVED — ver create_sequence/create_automation.

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_templates"
  }
}

Input Schema

Name	Required	Description	Default
`numero`	No	Etapa 1b — WhatsApp da conta (telefone, ex.: "5548992172321", ou o id em list_agent_profiles → numeros). Os modelos são da conta da Meta de cada número. Vazio = o número principal.
`target_user_id`	No	ID da conta-alvo (opcional; APENAS o admin da plataforma pode usar). Padrão: a conta autenticada.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / properties / numero

Added value: +{
+  "description": "Etapa 1b — WhatsApp da conta (telefone, ex.: \"5548992172321\", ou o id em list_agent_profiles → numeros). Os modelos são da conta da Meta de cada número. Vazio = o número principal.",
+  "type": "string"
+}

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description adds real context beyond that: templates are scoped per WhatsApp number / per Meta WABA account, and the returned approval states are enumerated (APPROVED, PENDING, REJECTED, PAUSED). No pagination or volume behavior is mentioned.

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 front-loaded sentences: identity/returned fields first, then the operational precondition. Dense and useful, with only a leading emoji as overhead.

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?

A read-only list tool with fully documented optional params, no output schema, and safety carried by annotations. The description fills the remaining gap by enumerating the approval statuses an agent will see and explaining why that status matters.

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 description coverage is 100%, so both 'numero' and 'target_user_id' are already documented, including the empty = primary-number default. The description only restates the per-WABA-account scoping; with the schema doing the heavy lifting, the baseline 3 applies.

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?

States a specific verb ('Lista') and resource ('templates de mensagem do WhatsApp Business da conta (WABA)'), plus what the listing carries (Meta approval status with the four enum values). An agent can distinguish it from create_whatsapp_template / send_whatsapp_template / delete_whatsapp_template without opening any schema.

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?

Gives a concrete when-to-use: before launching cadence/automation with cold WhatsApp sends (no open service window), which requires an APPROVED template, and points to create_sequence/create_automation as the downstream consumers. No explicit when-not-to-use or named alternative for the listing itself, so not a 5.

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

All Radar noEixo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?