Skip to main content
Glama
Sign In

Mojeeb

by app.mojeeb.mcp
OverviewDiscussionsAdmin

List a WhatsApp number's templates

list_whatsapp_templates
Read-onlyIdempotent

List a WhatsApp number's templates

Every template of one of the agent's WhatsApp numbers, read live from Meta, whatever its status: one item per language version, sorted by name, then language. Only approved templates can be sent. Each item says what POST /v1/whatsapp/templates must fill in: the body and header parameter keys in order, the header's format, and each button's index and the field that carries its value. It lists up to 100 templates.

Because it calls Meta every time, this endpoint allows 10 requests a minute per key, a budget the template endpoints share, counted apart from your other calls: keep the list, and read it again after your templates change. A connection that isn't a WhatsApp number is 404 not_found; a disconnected one is 409 connection_inactive, and one whose access Meta withdrew is 409 connection_needs_reconnection (reconnect it in the dashboard; retrying won't help). When Meta doesn't return the templates (an outage, a timeout or its own rate limit), the call is 503 meta_unavailable: retry with backoff.

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe agent the resource belongs to. Another company's agent, or the nil UUID, is `404 agent_not_found`; an agent outside the key's agent list is `403 agent_not_authorized`.
connection_idYesA connection of the agent. Another agent's connection is `404 not_found`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds the annotations: discloses the 10 req/min shared rate budget, the live-Meta read behavior, distinct 404/409/503 error conditions with remedies (reconnect for connection_needs_reconnection, backoff for meta_unavailable), and that retrying certain errors won't help. Annotations cover the safety profile, and the description layers substantial operational detail on top.

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 scope and return-shape, then rate limits and error semantics. Dense but nearly every sentence carries operational weight; only minor tightening would help.

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 output schema, the description does the work of describing returns (item granularity, sort order, the per-template send-parameter keys, the 100-item cap) and covers the full error surface. An agent has everything needed to call it and interpret failures.

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 100% and both required params (agent_id, connection_id) are already documented in the schema with their error behaviors. The description adds no input-side syntax beyond what the schema provides, so the baseline of 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 and resource ('List a WhatsApp number's templates') and immediately scopes it: all templates regardless of status, one item per language version, sorted by name then language. This clearly distinguishes it from the singular get_whatsapp_template and create/update siblings.

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 real usage context: read the list live, keep it, and re-read after templates change, plus the note that only `approved` templates can be sent. It does not explicitly name the get_whatsapp_template/update_whatsapp_template alternatives, so it stops short of full when/when-not routing.

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

All Mojeeb toolsInspect
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