Skip to main content
Glama

List WhatsApp templates

template_list
Read-onlyIdempotent

This organisation's WhatsApp message templates: id, name, language, category, Meta approval status and how many variables each takes. Only APPROVED templates can be sent. Read only.

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

Input Schema

NameRequiredDescriptionDefault
pageNo0-based page, default 0
sizeNoPage size, default 50
statusNoOnly templates in this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so 'Read only.' adds nothing and is mildly redundant. The valuable additions are the approval-status semantics and the fact that only APPROVED templates are sendable; nothing is said about pagination behavior or result ordering, which matters for a paged listing.

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?

Three short sentences, front-loaded with the resource and its fields. The closing 'Read only.' is the only clearly wasted clause since annotations already carry that signal.

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 returned fields and flags approval status, which is the key decision input for downstream sending. What remains thin is paging behavior (whether a total or cursor accompanies the page/size params), which an agent consuming a paged list would want.

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%, with page, size and status all documented including defaults and the status enum. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 applies.

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?

The description names the specific resource (this organisation's WhatsApp message templates) and enumerates the returned fields, so an agent knows this is a template inventory listing rather than a detail fetch. It does not explicitly contrast with the sibling template_detail, leaving the list-vs-single-record distinction to be inferred from the field enumeration.

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?

Usage is implied by 'Only APPROVED templates can be sent', which points toward the send flow, but the description never says when to call this versus template_detail or whatsapp_send_template. No exclusions or prerequisites are stated.

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.