Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

List WhatsApp message templates

list_message_templates
Read-only

List message templates for your WhatsApp Business Account with approval status, category, and language; filter by name or status to find the template name/language for send_template_message.

Instructions

List the message templates for your WhatsApp Business Account, including their approval status, category and language. Use this to find a template name/language to pass to send_template_message.

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

Input Schema

NameRequiredDescriptionDefault
nameNoFilter by (exact) template name
limitNoMax templates to return (1-100)
statusNoFilter by approval status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered; the description adds useful context beyond that by explaining that results carry approval status, category and language, which compensates for the missing output schema. It omits pagination behavior and what an empty result means, keeping it below a 5.

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?

Two short sentences, zero filler, with the resource and scope stated first and the routing advice second. Every sentence earns its place.

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

Completeness4/5

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

For a read-only list tool with three optional, fully documented parameters and annotations covering safety, the description supplies what an agent needs: what is returned and what to do with it next. Only minor gaps remain around result paging and the meaning of an empty list.

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 name, status and limit are already fully documented in the input schema. The description adds no filtering guidance (e.g., that status filtering is useful to find APPROVED templates before sending), so it meets the baseline without exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List the message templates for your WhatsApp Business Account" is a specific verb+resource, and it names the returned fields (approval status, category, language). The second sentence ties the tool to its follow-on (send_template_message), which implicitly separates it from the send_* siblings, though it never explicitly says it is read-only/does not send.

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?

"Use this to find a template name/language to pass to send_template_message" gives a concrete when-to-use condition and names the alternative tool. It stops short of stating when not to use it (e.g., to inspect template content or manage/edit templates elsewhere).

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