Turbo Notify: WhatsApp for AI agents

Send a message with a call-to-action link button

send_cta_button

Send an interactive message carrying one link button.

Set exactly one recipient: number, group_id, or contact_id.

A link button is the only interactive type WhatsApp accepts on this kind of connection. Reply buttons and list pickers are not available and will not become available, so do not try to emulate them.

body is the text above the button (up to 1024 characters), button_text its label (up to 20), header and footer optional short lines above and below (up to 60 each).

A message with a link button cannot be edited after it is sent: delete_message is the only change for it.

Input Schema

Name	Required	Description	Default
`body`	Yes	The text above the button, 1 to 1024 characters.
`footer`	No	A short line below the text, up to 60 characters.
`header`	No	A short line above the text, 1 to 60 characters.
`number`	No	Recipient phone number in E.164 form, digits only, country code first (e.g. `5511999999999`). Set exactly one of `number`, `group_id` or `contact_id`.
`group_id`	No	Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one inbox does not address the same group in another. Set exactly one of `number`, `group_id` or `contact_id`. Addressing a group needs a plan that includes group messaging: without it the call answers `payment_required: feature_not_available`, and retrying will not change that.
`button_url`	Yes	The link the button opens when the recipient taps it.
`contact_id`	No	Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one inbox does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
`button_text`	Yes	The label on the button, 1 to 20 characters.
`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
`idempotency_key`	No	Any printable ASCII text you choose, 1 to 255 characters, for example the id of the event you are answering. Reusing it for the same number suppresses a duplicate if you retry. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both.
`quoted_message_id`	No	Quote an earlier message (`msg_…`) so it appears above yours. Do this only when your text depends on something said a while ago, yours or theirs; do not quote the message you are answering right now, send a normal message instead.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent open-world send, so the safety profile is covered elsewhere. The description adds a genuinely non-obvious behavioral fact beyond that: a link-button message cannot be edited after sending and `delete_message` is the only remedy. It does not itself discuss retry/duplicate semantics, though the schema's idempotency_key field does.

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?

Four short paragraphs, front-loaded with the purpose and then the recipient rule, then constraints. Mild redundancy in re-quoting the character limits that already appear in the schema, but no wasted filler.

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 11 parameters, full schema descriptions, an output schema, and complete annotations, the description's remaining job is to convey the behavioral gotchas — immutability, recipient exclusivity, and the unavailable interactive types — all of which it does. Nothing needed to call it correctly 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 both the recipient and character-limit semantics are already documented in the schema. The description restates the 1024/20/60 limits and the header/body/footer positioning rather than adding anything new, which is the baseline case when the schema does the heavy lifting.

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?

"Send an interactive message carrying one link button" names a specific verb and resource and pins down the exact message shape. It also distinguishes this tool from the plain send_text / reply_to_message family by stating that a link button is the only interactive type available on this connection.

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?

It gives concrete selection rules: set exactly one of `number`, `group_id`, or `contact_id`, and explicitly rules out emulating reply buttons or list pickers. It does not name the sibling to use for plain text or quoted replies, so the routing back to send_text or reply_to_message is left implicit.

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.