Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

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

send_cta_button

Send a WhatsApp 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>",
      "button_text": "<button_text>",
      "button_url": "<button_url>"
    },
    "name": "send_cta_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe text above the button, 1 to 1024 characters.
footerNoA short line below the text, up to 60 characters.
headerNoA short line above the text, 1 to 60 characters.
numberNoRecipient 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_idNoRecipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number 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_urlYesThe link the button opens when the recipient taps it.
contact_idNoRecipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`.
button_textYesThe label on the button, 1 to 20 characters.
number_aliasNoWhich 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_keyNoAny 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, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both.
quoted_message_idNoQuote 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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / contact_id / description
      Previous value: -"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`."New value: +"Recipient contact id (`ct_…`), from `list_contacts`. A contact id belongs to one number: an id from one number does not address the same person in another. Set exactly one of `number`, `group_id` or `contact_id`."
    • changedInput schema / properties / group_id / description
      Previous value: -"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."New value: +"Recipient group id (`grp_…`), from `list_groups`. A group id belongs to one number: an id from one number 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."
  2. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"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."New value: +"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, but only for the same request: the same key with another recipient or another text is refused as idempotency_key_conflict and nothing is sent, so use a new key for each new message. Without it, retrying after a timeout may deliver the message twice, and the recipient sees both."
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare the write/open-world/non-idempotent profile, and the description goes beyond them with a genuine consequence: a link-button message cannot be edited after sending, and delete_message is the only change available for it. It also discloses a platform-level constraint (no other interactive types on this connection, ever), which is behavioral context an agent cannot derive from the schema. Idempotency and the group-plan payment_required failure are left to schema text rather than reinforced here.

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-loads verb and resource, then recipient rule, then the interactive-type constraint, then field semantics, then immutability — a sensible order with no filler. The paragraph-level formatting makes it scannable. The 'will not become available' clause is slightly over-emphatic but earns its place as an anti-workaround warning.

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?

With 11 parameters, no enums, and an output schema present, the description covers what the structured fields do not: recipient exclusivity at the call level, the immutability of the sent message, and the connection's interactive-type limits. Technical parameters such as number_alias, idempotency_key and quoted_message_id are left entirely to the schemas, which is acceptable at 100% coverage but means the description alone would not prepare an agent for retry or quoting decisions.

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 description coverage is 100%, so the schema already explains recipients, idempotency_key, quoted_message_id and number_alias in detail. The description restates the three-way recipient exclusivity and the character limits on body, button_text, header and footer, but adds no format, default, or failure semantics beyond what the schema carries. Baseline 3 applies.

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?

States a specific verb and resource up front: 'Send a WhatsApp message carrying one link button.' It also scopes the resource by declaring that a link button is the only interactive type accepted on this connection, which implicitly separates it from send_text and the reply-button siblings. It never names an alternative tool, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives useful negative guidance ('Reply buttons and list pickers are not available and will not become available, so do not try to emulate them') and a hard constraint on recipient selection, plus a pointer to delete_message as the only follow-up change. What it lacks is positive routing: it never says when to pick this over send_text or reply_to_message, leaving the agent to infer the choice from the button semantics.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.