whatsappTemplateListRead paginated native templates and cached template reporting for one owned WhatsApp account. Preserve exact name, language, components, approval and freshness; missing readings remain unknown. This never approves a template or enables analytics.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| cursor | No | ||
| accountPublicId | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Output schema / oneOfPrevious value: -[
- {
- "additionalProperties": false,
- "properties": {
- "ok": {
- "const": true,
- "type": "boolean"
- },
- "output": {
- "additionalProperties": false,
- "properties": {
- "cursor": {
- "anyOf": [
- {
- "maxLength": 4096,
- "type": "string"
- },
- {
- "type": "null"
- }
- ]
- },
- "done": {
- "type": "boolean"
- },
- "items": {
- "items": {
- "$ref": "#/$defs/__schema0"
- },
- "maxItems": 20,
- "type": "array"
- }
- },
- "required": [
- "cursor",
- "done",
- "items"
- ],
- "type": "object"
- },
- "toolName": {
- "const": "whatsappTemplateList",
- "type": "string"
- }
- },
- "required": [
- "ok",
- "output",
- "toolName"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "enum": [
- "INVALID_INPUT",
- "FORBIDDEN",
- "NOT_FOUND",
- "CONFLICT",
- "FEATURE_DISABLED",
- "CONFIRMATION_REQUIRED",
- "CONFIRMATION_INVALID",
- "UPSTREAM_FAILED",
- "NEEDS_REVIEW",
- "INTERNAL"
- ],
- "type": "string"
- },
- "message": {
- "maxLength": 2048,
- "minLength": 1,
- "type": "string"
- },
- "retryable": {
- "type": "boolean"
- }
- },
- "required": [
- "code",
- "message",
- "retryable"
- ],
- "type": "object"
- },
- "ok": {
- "const": false,
- "type": "boolean"
- },
- "toolName": {
- "const": "whatsappTemplateList",
- "type": "string"
- }
- },
- "required": [
- "error",
- "ok",
- "toolName"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "ok": {
+ "const": true,
+ "type": "boolean"
+ },
+ "output": {
+ "additionalProperties": false,
+ "properties": {
+ "cursor": {
+ "anyOf": [
+ {
+ "maxLength": 4096,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "done": {
+ "type": "boolean"
+ },
+ "items": {
+ "items": {
+ "$ref": "#/$defs/__schema0"
+ },
+ "maxItems": 20,
+ "type": "array"
+ }
+ },
+ "required": [
+ "cursor",
+ "done",
+ "items"
+ ],
+ "type": "object"
+ },
+ "toolName": {
+ "const": "whatsappTemplateList",
+ "type": "string"
+ }
+ },
+ "required": [
+ "ok",
+ "output",
+ "toolName"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "enum": [
+ "AI_SCHEDULING_LIMIT_REACHED",
+ "AI_SCHEDULING_UNAVAILABLE",
+ "INVALID_INPUT",
+ "FORBIDDEN",
+ "NOT_FOUND",
+ "CONFLICT",
+ "FEATURE_DISABLED",
+ "CONFIRMATION_REQUIRED",
+ "CONFIRMATION_INVALID",
+ "UPSTREAM_FAILED",
+ "NEEDS_REVIEW",
+ "INTERNAL"
+ ],
+ "type": "string"
+ },
+ "message": {
+ "maxLength": 2048,
+ "minLength": 1,
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "code",
+ "message",
+ "retryable"
+ ],
+ "type": "object"
+ },
+ "ok": {
+ "const": false,
+ "type": "boolean"
+ },
+ "toolName": {
+ "const": "whatsappTemplateList",
+ "type": "string"
+ }
+ },
+ "required": [
+ "error",
+ "ok",
+ "toolName"
+ ],
+ "type": "object"
+ }
+]Output schema / $defs / __schema1 / anyOfPrevious value: -[
- {
- "maxLength": 8192,
- "type": "string"
- },
- {
- "type": "number"
- },
- {
- "type": "boolean"
- },
- {
- "type": "null"
- },
- {
- "items": {
- "$ref": "#/$defs/__schema1"
- },
- "maxItems": 512,
- "type": "array"
- },
- {
- "additionalProperties": {
- "$ref": "#/$defs/__schema1"
- },
- "propertyNames": {
- "$ref": "#/$defs/__schema2"
- },
- "type": "object"
- }
-]New value: +[
+ {
+ "maxLength": 8192,
+ "type": "string"
+ },
+ {
+ "type": "number"
+ },
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ },
+ {
+ "items": {
+ "$ref": "#/$defs/__schema1"
+ },
+ "maxItems": 2000,
+ "type": "array"
+ },
+ {
+ "additionalProperties": {
+ "$ref": "#/$defs/__schema1"
+ },
+ "propertyNames": {
+ "$ref": "#/$defs/__schema2"
+ },
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive traits. The description adds meaningful context beyond them: it discloses cached reporting behavior, states that exact name/language/components/approval/freshness are preserved, and clarifies that missing readings remain unknown rather than being inferred.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences with the core purpose front-loaded and no wasted preamble. The middle sentence is dense but each clause conveys behavioral information that earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and annotations carry the safety profile. The remaining gap is parameter documentation: with 0% schema coverage and only implicit hints in the description, an agent still lacks detail on limit bounds and cursor format.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the schema documents no parameter semantics. The description partially compensates by signaling 'paginated' (implying cursor/limit) and 'one owned WhatsApp account' (implying accountPublicId scope), but gives no format, bounds, or syntax details for the three parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: reading native templates plus cached reporting for one owned WhatsApp account. Clearly distinct from sibling list tools like whatsappContactList and whatsappMediaList. No explicit naming of a sibling alternative, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Offers negative guidance ('This never approves a template or enables analytics') that implies when-not usage, but names no alternative tool or condition for choosing this over related siblings. Usage is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.