Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Send WhatsApp media message

send_media_message

Send WhatsApp images, videos, audio, documents, or stickers via a public HTTPS link or uploaded media ID, with optional captions for supported media types, within an open 24-hour service window.

Instructions

Send an image, video, audio, document or sticker, either by a public HTTPS link or by a media_id from upload_media. Captions are supported for image/video/document only. Requires an open 24-hour customer-service window.

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": {
      "to": "<to>",
      "media_type": "<media_type>"
    },
    "name": "send_media_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number, ideally E.164 (e.g. +971501234567)
linkNoPublic HTTPS URL of the media
captionNoCaption (image, video, document only)
filenameNoFile name shown for documents
media_idNoID returned by upload_media (use instead of link)
media_typeYesKind of media to send
reply_to_message_idNoOptional wamid of a message to reply to (shown as a quoted reply)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare openWorldHint and destructiveHint=false, so the description carries real weight: the 24-hour customer-service window prerequisite, the public-HTTPS requirement for links, and the caption restriction per media type. It omits return behavior and failure modes, which is acceptable given no output schema.

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

Conciseness5/5

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

Three short sentences, front-loaded with the capability, then sourcing paths, then the constraint. Every sentence conveys a distinct operational fact with no 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?

For a 7-parameter send tool with no output schema, it covers prerequisites, sourcing method, and media-type constraints well. The main remaining gap is what the call returns (message id/wamid), which an agent would need for follow-up like reply_to_message_id.

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 both required and optional fields are already documented, including the link-vs-media_id exclusivity and caption length. The description reinforces the two sourcing paths and the caption media-type restriction but adds no syntax or format detail beyond the schema; 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 (send) plus the resource (media message) and enumerates the supported media types, which incidentally separates it from send_text_message and send_template_message. It never names a sibling or explicitly contrasts with the text/template senders, so sibling differentiation is by implication only.

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 context: media can come from a public HTTPS link or a media_id returned by upload_media, and sending requires an open 24-hour customer-service window. It does not state the inverse case (e.g., outside the window use send_template_message), which would be the natural exclusion.

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