Skip to main content
Glama

whatsapp_templates_read

Read-onlyIdempotent

List the WhatsApp message templates of a number (name, language, category, approval status, components). Templates are required to message a customer outside the 24-hour window and for broadcast campaigns. Actions: list — all templates of the WhatsApp Business account

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>",
      "agentId": "<agentId>",
      "phoneId": "<phoneId>"
    },
    "name": "whatsapp_templates_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
actionYes
agentIdYes
phoneIdYesMeta WhatsApp phone number ID (from get_agent_channels), not the phone number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and openWorldHint=false, so safety is covered; the description adds that results are scoped to one number and enumerates what each template record contains (name, language, category, approval status, components). It omits pagination/limits, but the added data-shape context is genuine value beyond the annotations.

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?

Front-loaded with the core verb+resource and returned fields, then the business rationale, then the action enumeration. Three compact sentences with little waste, though the trailing "Actions: list" line is somewhat redundant with the leading verb.

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?

With no output schema, the description usefully enumerates the fields returned and explains the account-level scope of the list action. Remaining gaps are minor but real: no mention of which agent/account agentId identifies or whether results are paginated across languages and statuses.

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 coverage is 50%: phoneId and mode have solid schema descriptions, while agentId has none and action is a bare single-value enum. The description clarifies that "list" returns all templates of the WhatsApp Business account (i.e., no filtering), which adds meaning to action, but it says nothing about the required agentId or the compact/full mode tradeoff.

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?

States a specific verb and resource ("List the WhatsApp message templates") and scopes it to a single number, plus enumerates the returned fields. It is clearly a read/list operation, distinguishing it by verb from whatsapp_templates_write, though it never names that sibling explicitly.

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?

The description supplies business context (templates are needed to message outside the 24-hour window and for broadcast campaigns) and states the only action is "list — all templates of the WhatsApp Business account." That implies when to reach for it, but there are no explicit exclusions or pointers to alternative tools such as whatsapp_campaigns_read or whatsapp_numbers_read.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources