Skip to main content
Glama
wuapidev

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send an image, video, audio or document

send_media

Send media (image, video, audio, voice note, document, or sticker) from a public URL to a WhatsApp chat, with optional caption. Automatically downloads the URL and delivers it to the recipient.

Instructions

Send a file from a public URL: an image, video, audio, voice note (ogg/opus), document or sticker, with an optional caption. wuapi downloads the URL itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient: a phone number in E.164 with + (`+584241112233`), `lid:<digits>`, the `@username` of a contact the account already chats with, a group id (`...@g.us`), or a channel id (`...@newsletter`) the account administers.
urlYesPublic http(s) URL of the file. wuapi downloads it (up to 100 MB); private and internal addresses are refused.
typeYesWhat kind of file it is.
captionNoText shown with the file.
filenameNoDocuments: the file name the recipient sees.
mentionsNoContact ids to @mention (E.164 or `lid:<digits>`).
mimeTypeNoGuessed from the URL when omitted.
viewOnceNoImages, videos, audio and voice: can be opened once.
accountIdYesThe wuapi account id of the linked number to act as (from list_accounts).
idempotencyKeyNoOptional. Reuse the same key when retrying this exact call: within 24 hours wuapi returns the first result instead of doing it twice.
replyToMessageIdNoA wuapi message id in the same chat to quote (reply to).

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 already indicate readOnly=false and destructive=false, so the mutation nature is known. The description adds useful behavioral context: the file must be at a public URL and wuapi downloads it, which clarifies that the caller does not upload bytes. It does not describe side effects or return behavior, but the annotations lower the burden.

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?

Two sentences with no filler. The core action, supported types, and the key download behavior are front-loaded, making it easy for an agent to parse quickly.

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?

Given the rich schema covering all parameters and constraints (URL pattern, size limit, recipient formats, idempotency), the short description is adequate for the core call. It could mention that this sends a WhatsApp message or what the response contains, but no output schema exists and the schema carries most of the load.

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 fully documents all 11 parameters. The description adds little beyond restating 'optional caption' and the media types already present in the enum. This meets the baseline but does not exceed it.

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 description uses a specific verb ('Send') and resource ('a file from a public URL'), and enumerates the supported media types (image, video, audio, voice note, document, sticker). This clearly distinguishes it from siblings like send_text, send_location, send_contact, and send_poll.

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?

The description conveys a clear context: use this tool to send media files from a public URL, and notes that wuapi downloads the URL itself. However, it does not explicitly mention alternatives or when not to use it, leaving the choice versus send_text or post_story to inference.

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

Deploy Server

Other Tools