whatsappContactListRead paginated contacts for one owned WhatsApp account, with exact recipient IDs, current consent, suppression and customer-service window. Reading never grants consent or send eligibility; use the returned contact publicId in whatsAppTargets.
| 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": "whatsappContactList",
- "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": "whatsappContactList",
- "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": "whatsappContactList",
+ "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": "whatsappContactList",
+ "type": "string"
+ }
+ },
+ "required": [
+ "error",
+ "ok",
+ "toolName"
+ ],
+ "type": "object"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context beyond them: results are paginated, scoped to a single owned account, and reading has no consent/send-eligibility side effect. It stops short of describing pagination termination or error behavior.
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?
Two sentences, zero filler, with the core action and scope front-loaded before the downstream routing hint. Every clause carries information an agent needs.
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-value explanation is not required, yet the description still summarizes the payload. Ownership requirement, read-only semantics, and the downstream handoff are all present. It is only slightly thin on pagination mechanics and failure modes, which the output schema likely absorbs.
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% for three parameters (limit, cursor, accountPublicId). The description compensates partially: 'paginated' hints at limit/cursor and 'one owned' constrains accountPublicId to accounts the caller owns. However it gives no value ranges, cursor semantics, or format guidance, so the schema's max-20 limit and ID pattern remain undocumented.
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 ('Read paginated contacts') scoped to 'one owned WhatsApp account', and enumerates what the payload contains (recipient IDs, consent, suppression, service window). This cleanly separates it from siblings like whatsappMediaList and whatsappTemplateList without opening their schemas.
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?
Explicitly routes the agent downstream: 'use the returned contact publicId in whatsAppTargets.' It also sets a clear negative boundary ('Reading never grants consent or send eligibility'), which prevents a common misuse. It does not name a competing alternative tool, but no sibling duplicates contact listing, so context is clear enough.
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.