Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Server Details

Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
turbo-notify/agent-skills
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 36 tools

Disambiguation4/5

Most tools target a distinct resource and action, and descriptions clearly separate close pairs such as send_text versus reply_to_message, and get_message_status versus get_message_receipts. A few adjacent read/detail and quota tools could still be confused at a glance, but the boundaries are documented.

Naming Consistency5/5

Names consistently use snake_case with a clear verb_noun or verb_resource pattern: get_*, list_*, send_*, edit_*, delete_*, cancel_*, connect_*/disconnect_*. Even less standard cases like mark_as_read and react_to_message remain readable and fit the overall convention.

Tool Count2/5

36 tools is heavy for an agent-facing server, well above the typical 3-15 range. The broad WhatsApp domain justifies many of them, but several quota, picture, and message-detail tools add selection overhead and could potentially be consolidated.

Completeness4/5

Core messaging lifecycle coverage is strong: send multiple content types, reply, react, edit, delete, mark read, retrieve messages, status, receipts, reactions, events, numbers, contacts, and quotas. The main gaps are group administration (create group, add/remove participants) and broader contact management, which agents cannot perform through this surface.

Available Tools

36 tools
cancel_calendar_eventCancel a calendar event already sentA
Destructive
Inspect

Cancel a WhatsApp calendar event this number already sent.

The event stays in the chat marked as canceled, and WhatsApp tells the guests. Send the same name and start_at the event has, plus the details you want the canceled card to still show (description, end_at, join_link, location, has_reminder with reminder_offset_sec, extra_guests_allowed): the canceled event is shown with what you send here, and anything you leave out disappears from it.

Cancel when the date, time or place change and the guests must accept again: cancel the old event here, then send the new one with send_calendar_event, because the old answer does not carry over to a new event. To correct a mistake (a typo, the description, a link) use edit_calendar_event instead, and the guests keep their answer. A cancel does not change the entry a guest already added to their own calendar with the card's "Add to calendar" button. It stays on the old date, and adding again creates a second entry, which only the guest can delete.

Only a calendar event can be canceled. Using this tool on any other message answers invalid_request: message_not_editable; to take back a message of another kind, use delete_message.

Only a message sent THROUGH Turbo Notify can be canceled. One typed on the phone itself belongs to the same number but cannot be canceled here, and neither can a message received from someone else.

The 15-minute limit for a text or a caption does not apply to a calendar event.

The cancel is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the cancel happens. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: name (required), start_at (required), message_id (required), end_at, +7 more. Returns: object

connect_numberBring a number back onlineA
Idempotent
Inspect

Reconnect a WhatsApp number that is currently offline.

Uses the credentials already stored for the number, so no QR code and no human are involved. Use it when get_number reports disconnected and you want to send.

Returns immediately, before the connection is established. The answer has the number's alias, status set to connecting and at, the moment the request was accepted. The number reaches connected a few seconds later: poll get_number, which stays the source of the current status and of its own at, rather than assuming it worked.

It works the same on every number and never charges. On an extra number scheduled for removal it does not change the removal: the number keeps working until its date. Cancelling a removal is not available to agents.

This cannot rescue a revoked number: WhatsApp ended that link and a person with the phone has to pair it again.

Calling it again changes nothing further. A number that is already connected or connecting answers with an already_connected or already_connecting error, which means the goal is met, not that the call failed.

Inputs: number_alias. Returns: object

delete_messageDelete a message for everyoneA
Destructive
Inspect

Revoke a WhatsApp message for everyone in the conversation.

This is WhatsApp's "delete for everyone". It is not reversible, and recipients see a tombstone where the message was, so they can tell something was deleted. Confirm with a human before using it on anything a person has plausibly already read.

The number first appears online and its unread messages in that conversation are marked as read, then the message is deleted. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: message_id (required), number_alias. Returns: object

disconnect_numberTake a number offline without unlinking itA
Idempotent
Inspect

Take a WhatsApp number offline on purpose, keeping its link to the phone.

The stored credentials survive, so connect_number brings it straight back with no pairing. Nothing is deleted. Disconnecting does not stop billing: an extra number is billed every cycle until it is removed.

Returns immediately, before the number is offline. The answer has the number's alias, status set to disconnecting and at, the moment the request was accepted. disconnecting is not a status that get_number reports: it keeps showing the previous status and its own at until the number is offline.

While disconnected the number cannot send: a send, reply or reaction through it is refused at once with number_not_connected, never held to go out later. It receives nothing until it is connected again.

Calling it again changes nothing further. A number that is already offline answers with an already_disconnected error, which means the goal is met, not that the call failed.

Inputs: number_alias. Returns: object

edit_calendar_eventEdit a calendar event already sentA
Destructive
Inspect

Correct a WhatsApp calendar event this number already sent.

name and start_at are always required, plus whatever else the event has: description, end_at, join_link, location, has_reminder with reminder_offset_sec, and extra_guests_allowed. This REPLACES the whole event: anything you leave out is removed from it, including its location, reminder and guest setting, so send again every detail you want to keep. The event keeps its place in the chat and the guests keep the answer they already gave.

Use an edit to fix a mistake (a typo, the description, a link). When the date, time or place change and the guests must accept again, do not edit: cancel the event with cancel_calendar_event and send a new one with send_calendar_event, because the old answer does not carry over to a new event. Neither an edit nor a cancel changes the entry a guest already added to their own calendar with the card's "Add to calendar" button. It stays on the old date, and adding again creates a second entry, which only the guest can delete.

Only a calendar event can be edited here. Using this tool on any other message answers invalid_request: message_not_editable.

Only a message sent THROUGH Turbo Notify can be edited. One typed on the phone itself belongs to the same number but cannot be edited here, and neither can a message received from someone else.

The 15-minute limit does not apply to a calendar event.

The edit is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the edit happens. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: name (required), start_at (required), message_id (required), end_at, +7 more. Returns: object

edit_media_captionEdit the caption of an image, video or documentA
Destructive
Inspect

Replace the caption of a WhatsApp image, video or document this number already sent.

The recipient sees the new caption marked as edited. The file itself stays exactly as it was and the message keeps its id: only the caption changes. There is no way to replace the file; to send a different one, send a new message with send_media.

Only an image, video or document can be edited this way. Audio and stickers have no caption, and a location, contact card or link button cannot be edited at all: delete_message is the only change for them. For the text of a text message use edit_text_message. Using this tool on any other message answers invalid_request: message_not_editable.

Only a message sent THROUGH Turbo Notify can be edited. One typed on the phone itself belongs to the same number but cannot be edited here, and neither can a message received from someone else.

WhatsApp only accepts a change to a caption within 15 minutes of sending it. A later edit is refused up front with invalid_request: edit_window_expired; send a new message instead.

The edit is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the edit happens. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: caption (required), message_id (required), number_alias. Returns: object

edit_text_messageEdit the text of a message already sentA
Destructive
Inspect

Replace the text of a WhatsApp text message this number already sent.

The recipient sees the new text marked as edited. The message keeps its id and its place in the conversation; only the text changes.

Only a text message can be edited here. For the caption of an image, video or document use edit_media_caption, and for a calendar event edit_calendar_event or cancel_calendar_event. A location, contact card, link button, sticker or audio message cannot be edited at all: delete_message is the only change for them. Using this tool on any message that is not text answers invalid_request: message_not_editable.

Only a message sent THROUGH Turbo Notify can be edited. One typed on the phone itself belongs to the same number but cannot be edited here, and neither can a message received from someone else.

WhatsApp only accepts a change to a text within 15 minutes of sending it. A later edit is refused up front with invalid_request: edit_window_expired; send a new message instead.

The edit is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the edit happens. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: text (required), message_id (required), number_alias. Returns: object

get_contactGet one contactA
Read-onlyIdempotent
Inspect

Fetch one WhatsApp contact: name, phone number and activity timestamps.

first_messaged_at is when a message from this number first reached them on WhatsApp, and last_interaction_at is the last message that passed in EITHER direction, so it moves when they write to you as well. A message that failed before reaching WhatsApp moves neither.

refresh shows the last refresh_contact you asked for: when it was requested, when it finished, and its outcome (updated, unchanged, number_not_connected or unavailable). While completed_at is null it is still running.

The id must belong to the number named by number_alias. An id from a different number returns not found even though the person exists.

Inputs: contact_id (required), number_alias. Returns: object

get_contact_profile_pictureGet a contact's profile pictureA
Read-onlyIdempotent
Inspect

Get a WhatsApp contact's profile picture, or the reason there is none.

The answer carries kind: available with a temporary URL, or unavailable with a reason. no_storage means the organization has not configured object storage, which is a setup step rather than a fault with this contact. The person may also simply have no picture, or have hidden it in their privacy settings.

Inputs: contact_id (required), number_alias. Returns: object

get_contact_quotaGet a number's contact quota for this billing cycleA
Read-onlyIdempotent
Inspect

Check how much of this WhatsApp number's contact allowance is left.

A contact counts once per billing cycle when this number messages them through Turbo Notify, new or returning. Messaging the same person again in a later cycle counts again.

Like the message quota, this is per number rather than per organization, and it resets at cycle_end.

Inputs: number_alias. Returns: object

get_groupGet one groupA
Read-onlyIdempotent
Inspect

Fetch a WhatsApp group: its name, description, picture and settings.

Returns how many participants it has, not who they are. Membership is not readable here: it arrives as it changes, on the group.participants_added / _removed / _promoted / _demoted events, which list_events can read.

Inputs: group_id (required), number_alias. Returns: object

get_group_pictureGet a group's pictureA
Read-onlyIdempotent
Inspect

Get a WhatsApp group's picture, or the reason there is none.

Same shape as a contact's picture. The answer carries kind: available with a temporary URL, or unavailable with a reason. no_storage means the organization has not configured object storage.

Inputs: group_id (required), number_alias. Returns: object

get_messageGet one message in fullA
Read-onlyIdempotent
Inspect

Fetch one WhatsApp message with its full content, parties and mentions.

The answer includes the number's stable number_id (num_…) next to number_alias.

at is when the message actually happened on WhatsApp; status.at is when it reached its current delivery status and keeps moving as receipts arrive. They answer different questions and are not interchangeable.

Returns not found if the id belongs to a different number. Past the organization's content retention window (1 hour by default, up to 72 hours depending on the plan) the message is still returned, with content_expired true and its content empty.

Inputs: message_id (required), number_alias. Returns: object

get_message_quotaGet a number's message quota for this billing cycleA
Read-onlyIdempotent
Inspect

Check how much of this WhatsApp number's message allowance is left.

The quota is per number, not per organization: an organization with three numbers has three separate allowances. It resets at cycle_end, which is the organization's real billing boundary rather than a rolling window, so resets_at is a date you can plan around.

Only messages sent through Turbo Notify consume it. Messages someone sends from the phone itself do not.

Inputs: number_alias. Returns: object

get_message_reactionsGet the reactions on a messageA
Read-onlyIdempotent
Inspect

List the emoji reactions on a WhatsApp message, and who left each one.

Each entry names the reactor and the emoji. Reactions are replaced rather than accumulated per person: someone who reacts twice leaves one entry showing their latest emoji, so this is a current snapshot and not a history.

An empty list is the normal answer for most messages, and is not an error.

Inputs: message_id (required), number_alias. Returns: object

get_message_receiptsGet per-recipient delivery and read receiptsA
Read-onlyIdempotent
Inspect

See who received and who read a WhatsApp message.

Most useful for group messages, where the single status on the message cannot express that some members read it and others have not.

Requires a plan that includes read receipts; on plans without it the call is refused with feature_not_available, which no retry will fix.

Inputs: message_id (required), number_alias. Returns: object

get_message_responsesGet the guests' answers to a calendar eventA
Read-onlyIdempotent
Inspect

See how the guests answered a WhatsApp calendar event: going, not going or maybe.

Only works on a calendar event; any other message answers invalid_request: message_not_calendar.

The answer has counts (how many guests are going, not going or maybe, and how many extra guests those who are going or maybe are bringing) and responses, one entry per guest with who they are, their answer, any extra guests they bring and when they answered. A guest who changes their mind leaves one entry showing the latest answer, so this is a current snapshot and not a history. To be told as answers come in, watch for message.calendar_responded with list_events.

An event nobody has answered yet returns zero counts and an empty list, which is the normal answer and not an error.

Inputs: message_id (required), number_alias. Returns: object

get_message_statusGet a message's delivery statusA
Read-onlyIdempotent
Inspect

Check where a WhatsApp message got to: queued, sent, delivered, read, failed.

Status only moves forward. A failed status always carries an error code, and for a few media and reaction problems it also carries a hint naming the field to change; most failures give the code alone. Read the code before retrying, because most failures repeat identically.

Inputs: message_id (required), number_alias. Returns: object

get_numberGet one number and its connection statusA
Read-onlyIdempotent
Inspect

Check one WhatsApp number: its phone number, status, and when that status began.

id (num_…) is the number's permanent identifier. The alias can be renamed, the id cannot. Either one works as number_alias.

connected means it can send right now. connecting means a connection was just requested and is being set up; check again in a few seconds. reconnecting means the number lost its connection and Turbo Notify is bringing it back by itself: there is nothing to do but wait and check again. Until it is connected again, sends are refused with number_not_connected. disconnected means the link to the phone still exists but the number is offline, so connect_number brings it back. inactive is the same for a number that was linked and has not been brought online yet: connect_number brings it online too. pending means the number was never linked to a phone, and no_main_number (what a brand-new account gets for main, and list_numbers is empty) means there is no number at all yet: either way a person has to link it from the Numbers page of the dashboard, so tell them and do not retry the send meanwhile. revoked means WhatsApp ended the link (the device was removed under Linked devices on the phone, or the phone went more than 14 days without being used) or another connection took it over. failed means a pairing did not complete; on an extra number reason says why (for example pairing_timeout when the code or QR code was not used in time, paired_phone_mismatch when another WhatsApp used it). Either one has to be paired again by a person holding that phone: from the dashboard (main or extra number) or, for an extra number, through the API's pairing endpoint, by code or by QR code. No tool here pairs a number: it needs a person with the phone.

pairing means a person is pairing the number right now. The code or QR code they use is not part of this answer: it belongs to that person. Check again later; the status moves to connected, or to failed (with a reason on an extra number).

Inputs: number_alias. Returns: object

get_usageGet the organization's usage across all numbersA
Read-onlyIdempotent
Inspect

Get WhatsApp message and contact usage for the whole organization.

The top-level totals are the sum across every live number: an organization with two numbers on a 50,000-message plan reports a quota of 100,000, not 50,000. The numbers[] breakdown shows each number separately, which is what you need to find the one that is close to its own ceiling, so a healthy-looking total can hide a number at 99%.

For one number, get_message_quota and get_contact_quota are more direct.

Inputs: no named parameters. Returns: object

list_contactsList the contacts of a WhatsApp numberA
Read-onlyIdempotent
Inspect

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.

Inputs: name, limit, phone, cursor, +3 more. Returns: object

list_eventsList what happened on the organization's WhatsApp numbersA
Read-onlyIdempotent
Inspect

Poll everything that happened on the organization's WhatsApp numbers: messages, contacts, groups, numbers, quotas.

This is how an agent learns about inbound messages without hosting a webhook endpoint.

Events come back newest first, so polling for new ones uses ending_before, not starting_after. Typical loop: call with no cursor and remember the id of the FIRST event in the page (the newest one); next time, pass that id as ending_before to get only what has happened since. An empty page means you are caught up.

starting_after does the opposite: it walks BACKWARD into history, which is what you want for reading older events, and never what you want for noticing something new. Passing the last id you handled to starting_after in a loop returns steadily older events and never reaches the present.

request_id returns everything that came of one earlier call. A write tool's result carries request_id when the platform issued one; keep it and you can ask later what became of that specific send.

number_id restricts to one number and keeps matching its events after the number is renamed. number_alias restricts to one number by the alias it had when the event happened, so a rename hides the older events; the two can be combined. Either one excludes storage.* and media.unavailable events, which belong to the organization rather than to any one number.

Most events carry a number_alias telling you which number they belong to, and number_id (num_…), the same number's permanent identifier. The alias is the one at the time of the event and can be renamed later; the number_id cannot. You need one of them: message, contact and group ids are unique but not self-addressing, so an id alone does not tell you which number's tools to use with it, and both work as number_alias in the other tools. Read the fields defensively rather than assuming they are there: storage.* and media.unavailable belong to the organization as a whole and have no single number to name, so on those the keys are absent rather than empty.

Inputs: limit, number_id, event_type, request_id, +6 more. Returns: object

list_groupsList the groups a number belongs toA
Read-onlyIdempotent
Inspect

List the WhatsApp groups this number is a member of.

The list is built when the number connects: every group it belongs to is picked up then, whether or not anything has been said in it. A group joined since then is picked up from the join itself, without waiting for anyone to speak in it.

name filters by group name. include_left=true also returns groups this number has left, which are otherwise hidden.

Inputs: name, limit, cursor, include_left, +1 more. Returns: object

list_messagesList the messages of a WhatsApp numberA
Read-onlyIdempotent
Inspect

List messages for one number, newest first, received and sent.

Each item says who it is from and to, which number it belongs to, its direction, content_type, origin, a short preview, at, status and content_expired. Mentions, transcription and full media detail are only on get_message, so fetch the one message you care about rather than paging for detail.

To read a group, find its grp_ id with list_groups and pass it as group_id. contact_id returns what that contact sent or received, which in a group includes what they said there. direction keeps only inbound or outbound. Filters combine: group_id with contact_id answers what one person said in one group.

Ids belong to one number, so use the same number_alias you got them from: an id from another number answers not found. For the next page, pass back the cursor from the previous response together with the same filters.

Content older than the plan's retention window comes back with preview empty and content_expired true. The message, its sender and its group stay listed for 12 months.

Inputs: limit, cursor, group_id, direction, +2 more. Returns: object

list_numbersList the organization's WhatsApp numbersA
Read-onlyIdempotent
Inspect

List every WhatsApp number this organization has, with its status.

Start here when you do not know which aliases exist. The main number is always main; extras carry the alias the customer chose, and that alias is what every other tool's number_alias expects.

Each number also carries id (num_…), which never changes, even when the alias is renamed. Keep it if you need to recognise a number later: events carry the same value as number_id, and the other tools accept either one as number_alias. To find the numbers that need attention, pass status, for example disconnected.

Only connected numbers can send. status.at is when the number entered its current state, which is how you tell a fresh disconnection from one that has been down for hours.

Inputs: status. Returns: object

mark_as_readMark a WhatsApp conversation as readAInspect

Mark a conversation's unread messages as read, without sending anything.

Set exactly one recipient: number, group_id, or contact_id. With number or contact_id, only the one-to-one chat with that person is marked as read: the messages they sent in groups stay unread. For a group, pass its group_id.

This is independent of the automatic mark-as-read that already happens when you send, reply, react, edit, delete or start typing (the number also appears online first): use it to clear an unread badge on its own, for example when handing a conversation to a human who has already seen it. No message is sent and no message.* event is produced, but the sender sees the messages as read (blue ticks) on WhatsApp.

Needs a plan that includes read receipts (BUSINESS and above). Without it this answers payment_required: feature_not_available, and the answer will not change by retrying.

Inputs: number, group_id, contact_id, number_alias. Returns: object

react_to_messageReact to a message with an emojiAInspect

Attach an emoji reaction to a WhatsApp message, or remove one.

Pass a single emoji character, e.g. 👍. Passing an empty string removes the reaction this number previously left. A new emoji replaces this number's previous reaction rather than adding beside it; to bring the earlier one back, react with it again.

Works on messages in either direction: reacting to something a customer sent is often a cheaper acknowledgement than a reply.

The number first appears online and its unread messages in that conversation are marked as read, then the reaction is sent. Opening the conversation this way is automatic and uses no quota of its own.

Needs a plan that includes reactions. On a plan that does not, this answers payment_required: feature_not_available, and the answer will not change by retrying.

Inputs: emoji (required), message_id (required), number_alias. Returns: object

refresh_contactRefresh a contact's WhatsApp nameAInspect

Ask WhatsApp for this contact's current name.

Only the name is refreshed. The profile picture updates on its own the next time this number exchanges a message with the contact, and this does not change how messages reach them.

It answers right away with requested_at; the refresh then runs in the background. Call get_contact and read refresh: when completed_at is set, outcome says what happened (updated means the name changed, unchanged means it was already current, number_not_connected means the number was offline, unavailable means WhatsApp did not answer).

This is the one contact tool that is not read-only: it queries WhatsApp over the live connection and spends the organization's per-minute refresh budget, so it needs a key with contacts write access. Do not call it in a loop over a list. Refresh the one contact whose name looks stale.

Inputs: contact_id (required), number_alias. Returns: object

reply_to_messageReply to a message in the same conversationAInspect

Reply on WhatsApp to an EARLIER message, quoting it, without naming a recipient.

Use it to bring context into the conversation: when the conversation has moved on and your answer depends on something said a while ago (by the contact, by you or, in a group, by any participant). To answer the message you just received, do not use this tool: send a normal message with send_text and let the chat carry the context, as a person would.

The recipient is worked out from the original: an inbound message is answered to its sender, an outbound one to whoever received it, and a group message to the group.

The message must belong to the number named by number_alias; a message_id from a different number returns not found.

Like a person opening the chat, the number first appears online and its unread messages in that conversation are marked as read, then the reply is sent. Opening the conversation this way is automatic and uses no quota of its own.

Inputs: text (required), message_id (required), number_alias, idempotency_key. Returns: object

send_calendar_eventSend a calendar eventAInspect

Send a WhatsApp calendar event invitation.

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

start_at and end_at are ISO 8601 with an offset, for example 2026-09-10T14:00:00Z. A timestamp without one is rejected: the recipient's phone renders the event in their own timezone, so an ambiguous instant would show the wrong hour on their screen.

When set, end_at must be after start_at; an event that ends before (or exactly when) it starts is rejected.

location pins where it happens (latitude and longitude, with an optional name and address). has_reminder reminds guests, and reminder_offset_sec says how many seconds before the event; extra_guests_allowed lets guests bring extra people.

To fix a mistake later (a typo, the description, a link), use edit_calendar_event: guests keep their answer. When the date, time or place change and guests must accept again, cancel the event with cancel_calendar_event and send a new one with this tool. The entry a guest added to their own calendar with the card's "Add to calendar" button never follows an edit or a cancel: it stays on the old date and adding again creates a second entry, so tell guests to delete the old one. To see who said they are coming, use get_message_responses.

Inputs: name (required), start_at (required), end_at, number, +11 more. Returns: object

send_contact_cardSend a contact cardAInspect

Send a WhatsApp contact card the recipient can save to their phone.

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

phones takes plain E.164 numbers, 1 to 10 of them. emails, organization, title and address are optional extra fields on the card; emails allows up to 10 as well.

A contact card cannot be edited after it is sent: delete_message is the only change for it.

Inputs: phones (required), display_name (required), title, emails, +8 more. Returns: object

send_cta_buttonSend a message with a call-to-action link buttonAInspect

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.

Inputs: body (required), button_url (required), button_text (required), footer, +7 more. Returns: object

send_locationSend a map locationAInspect

Send a WhatsApp location pin.

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

latitude is between -90 and 90, longitude between -180 and 180. name and address label the pin; url adds a link beside it.

A location cannot be edited after it is sent: delete_message is the only change for it.

Inputs: latitude (required), longitude (required), url, name, +7 more. Returns: object

send_mediaSend an image, video, audio, document or stickerAInspect

Send an image, video, audio clip, document or sticker on WhatsApp, from a URL.

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

url must still be reachable when the send happens: Turbo Notify fetches the bytes from it. A copy is kept in the organization's own object storage afterwards when that is configured, which never blocks the send and is not required for one.

caption applies to image, video and document only; audio and stickers have nowhere to render one. filename applies to document only. Pairing either with a kind that cannot carry it is rejected here, before anything is sent.

After sending, only the caption of an image, video or document can be changed, with edit_media_caption. The file itself, an audio clip and a sticker cannot be edited: delete_message is the only change for them.

mime_type is optional and does not change how the message is sent. The type WhatsApp receives comes from what the URL's own server serves, so point url at a file that server labels correctly.

Inputs: url (required), kind (required), number, caption, +7 more. Returns: object

send_textSend a text messageAInspect

Send a WhatsApp text message.

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

Writing @<number> in the text mentions that person, for example @5511999999999. The platform detects it automatically; there is no separate mentions argument.

This is also how to answer the message you just received: a normal message to its sender, as a person does in a chat, with no quote. Quote (quoted_message_id, or reply_to_message) only an earlier message that your answer depends on.

A text message you sent can be corrected later with edit_text_message.

Like a person opening the chat, the number first appears online and its unread messages in that conversation are marked as read, then the message is sent. Opening the conversation this way is automatic and uses no quota of its own.

Returns the new message_id and its initial status. Delivery happens asynchronously; poll get_message_status or watch list_events for the outcome.

Inputs: text (required), number, group_id, contact_id, +3 more. Returns: object

send_typing_indicatorShow the typing indicator in a conversationAInspect

Show "typing…" to a recipient on WhatsApp while you prepare an answer.

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

Useful before a reply that takes a few seconds to compose, so the person on the other end sees something is happening. It expires on its own, so clearing it is optional: pass is_typing=false only if you decide not to answer after all and want the indicator gone at once.

There is no duration argument. WhatsApp decides how long it lives.

Starting to type also opens the conversation: the number appears online, its unread messages in that conversation are marked as read, and after a short pause "typing…" appears, so it never shows over unread messages. Stopping (is_typing=false) only clears the indicator and reads nothing. Opening the conversation this way is automatic and uses no quota of its own.

Needs a plan that includes the typing indicator, and showing it in a group needs one that includes group messaging as well. Without either, this answers payment_required: feature_not_available, and the answer will not change by retrying.

Inputs: number, group_id, is_typing, contact_id, +1 more. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      WA MCP is a hosted WhatsApp MCP server. It connects your own WhatsApp number to Claude, Claude Code, ChatGPT, Grok Bot, Cursor or any MCP client. Free plan with no time limit, nothing to install.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to control WhatsApp, including sending messages and media, reading chats, managing groups and communities, with QR/pairing auth and session persistence.
      14
      15 npm
      2
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.