Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Send an image, video, audio, document or sticker

send_media

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.

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": {
      "kind": "<kind>",
      "url": "<url>"
    },
    "name": "send_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink to the file to send. It must still be reachable when the message goes out.
kindYesWhat the file is: image, video, audio, document or sticker.
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`.
captionNoText shown with an image, video or document, up to 1024 characters. Audio and stickers cannot carry one.
filenameNoThe file name the recipient sees on a document, up to 255 characters. Documents only.
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.
mime_typeNoThe media's MIME type, recorded alongside the message. It does not change how the file is sent: the type WhatsApp receives comes from what the URL's own server serves. Optional.
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`.
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

A4.6/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, non-destructive, non-idempotent open-world call; the description goes well beyond that by disclosing that the URL is fetched at send time and must still be reachable, that a copy lands in the org's object storage without blocking, and that invalid caption/filename combinations are rejected before anything is sent. It also maps the post-send lifecycle: only captions are editable, and the file, audio and stickers are immutable except by delete_message.

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?

Short paragraphs, each covering one concern in a sensible order (what it does, recipient rule, URL lifecycle, caption/filename rules, editability, mime_type), with no filler sentences. Some sentences restate schema text, which adds bulk but not confusion.

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?

For an 11-parameter mutation tool with an output schema and full annotation coverage, the description supplies exactly the non-obvious parts an agent needs: recipient exclusivity, URL reachability timing, argument/kind pairing validation, and what can be edited afterward. Remaining details (idempotency, alias selection) are fully covered by schema descriptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description adds real meaning: mime_type is explicitly a no-op for delivery because the type is derived from the URL's server, and caption/filename applicability is framed as a pre-send validation rule rather than a soft note. It does not discuss number_alias or idempotency_key, but those are documented in the schema.

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?

The first sentence names a specific verb (Send) plus the exact resource set (image, video, audio clip, document, sticker) on a named channel (WhatsApp) and the sourcing constraint (from a URL). This cleanly separates it from send_text, send_location, send_contact_card and send_cta_button without the agent needing to open any schema.

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 an explicit routing constraint — 'Set exactly one recipient: number, group_id, or contact_id' — and names the follow-up alternatives edit_media_caption for caption changes and delete_message as the only change for audio/stickers. It never states a negative case (e.g. use send_text for plain text), so the exclusions are implied rather than spelled out.

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.