Turbo Notify: WhatsApp for AI agents

List an inbox's contacts

list_contacts

Read-onlyIdempotent

List the people this number has exchanged messages with.

Filter by phone or by name. They are separate filters, not one search box: name matches the contact's name, phone matches the number.

source restricts to how the contact first appeared: inbound (they messaged this number), outbound (this number messaged them), mention (named in a group message) or self (the number's own contact card).

contacted_in_cycle=true narrows the list to exactly the people counting against this number's contact quota this billing cycle: those messaged through Turbo Notify inside the cycle, whether newly or again. Use it to see what the quota gauge is actually counting.

Input Schema

Name	Required	Description	Default
`name`	No	Only contacts whose name matches.
`limit`	No	How many items to return, 1-200. Defaults to 50.
`phone`	No	Only contacts whose phone number matches.
`cursor`	No	Opaque cursor for the next page. Pass back the `cursor` from the previous response, with the same filters; omit it for the first page.
`source`	No	Only contacts that first appeared this way: `inbound` (they messaged this number), `outbound` (this number messaged them), `mention` (named in a group message) or `self` (the number's own contact card).
`number_alias`	No	Which of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.	main
`contacted_in_cycle`	No	When true, return only the people who count against this number's contact quota in the current billing cycle: those messaged through Turbo Notify inside the cycle, new or returning. Use it to see exactly what the quota figure is counting.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real domain context beyond that: what 'first appeared' means per source value, and precisely which population counts against the billing-cycle quota. Pagination behavior is left to the schema rather than the prose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and readable, with the core purpose in the first sentence. However, the source paragraph duplicates the schema's enum descriptions nearly word-for-word, and the contacted_in_cycle explanation is given twice within the same description, which is avoidable repetition.

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?

An output schema exists, so return shape needn't be explained, and cursor semantics live in the schema. For a seven-parameter filtered list tool the description covers the non-obvious parts (quota population, source meanings). It is slightly short on how limit interacts with the quota view, but nothing critical is missing.

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%, so the baseline is 3. The description does contribute one genuinely additive clarification — that name and phone are independent filters rather than a single fuzzy search — but the source enumeration paragraph essentially restates the enum description already in the schema, and limit/cursor/number_alias get no prose treatment.

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 opening line states a specific verb and resource ('List the people this number has exchanged messages with'), which cleanly separates it from the singular sibling get_contact. It does not name any sibling outright, so the differentiation is implied by list-vs-get rather than stated.

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 concrete guidance on how the filters compose (name and phone are separate, not a combined search box) and explains the exact scenario for contacted_in_cycle=true ('use it to see what the quota gauge is actually counting'). It stops short of naming get_contact as the alternative for looking up one person, and never states when not to use this list tool.

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

All Turbo Notify: WhatsApp for AI agents tools Inspect

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.