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 a file: an image, video, audio, voice note (ogg/opus), document or sticker, with an optional caption. Give exactly one of url (a public URL wuapi downloads itself) or uploadId (a file uploaded before with upload_file).

Instructions

Send a file: an image, video, audio, voice note (ogg/opus), document or sticker, with an optional caption. Give exactly one of url (a public URL wuapi downloads itself) or uploadId (a file uploaded before with upload_file). Images go out at the account's image quality (standard by default, as WhatsApp sends a photo); pass quality to change it for one image, or send the file as a document to deliver it untouched.

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.
urlNoPublic 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.
qualityNoImages only: the quality of this image instead of the account's. `hd` is WhatsApp's HD photo; `original` sends the file without re-encoding it.
filenameNoDocuments: the file name the recipient sees.
mentionsNoContact ids to @mention (E.164 or `lid:<digits>`).
mimeTypeNoGuessed from the URL, or the upload's own type, when omitted.
uploadIdNoThe id of an upload made with upload_file (or `POST /v1/uploads`): a file wuapi already stores. Usable for 24 hours, any number of times.
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). One exception, a private reply: a message someone else wrote in a group can be quoted in the direct chat with its author (`to` is that message's `from`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.1
    • changedInput schema / properties / replyToMessageId / description
      Previous value: -"A wuapi message id in the same chat to quote (reply to)."New value: +"A wuapi message id in the same chat to quote (reply to). One exception, a private reply: a message someone else wrote in a group can be quoted in the direct chat with its author (`to` is that message's `from`)."
  2. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / mimeType / description
      Previous value: -"Guessed from the URL when omitted."New value: +"Guessed from the URL, or the upload's own type, when omitted."
    • addedInput schema / properties / quality
      Added value: +{
+  "description": "Images only: the quality of this image instead of the account's. `hd` is WhatsApp's HD photo; `original` sends the file without re-encoding it.",
+  "enum": [
+    "standard",
+    "hd",
+    "original"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / uploadId
      Added value: +{
+  "description": "The id of an upload made with upload_file (or `POST /v1/uploads`): a file wuapi already stores. Usable for 24 hours, any number of times.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "accountId",
-  "to",
-  "type",
-  "url"
-]New value: +[
+  "accountId",
+  "to",
+  "type"
+]
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower, and the description still adds behavioral context the schema only partly covers: images are re-encoded at the account's quality by default ('as WhatsApp sends a photo'), and the document path avoids that. It does not discuss the non-idempotent nature versus the idempotencyKey escape hatch, rate limits, or permissions.

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 front-loaded sentences: purpose and file kinds, then the source constraint, then the image-quality behavior. No filler, no restatement of the title, and every clause carries actionable information.

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 13 parameters at 100% schema coverage and no output schema, the structured data carries most of the load; the description covers purpose, the url/uploadId exclusivity, and image-quality defaults. It is complete enough to call correctly, though it omits retry/idempotency guidance that matters for a non-idempotent send.

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 description coverage is 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint the schema does not express: 'Give exactly one of `url` ... or `uploadId`'. That is the kind of relational rule an agent cannot infer from per-field descriptions alone.

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?

States a specific verb and resource ('Send a file: an image, video, audio, voice note, document or sticker') and enumerates the supported media kinds, distinguishing it from send_text, send_location, send_poll and upload_file. An agent can identify the tool's job without opening the 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?

Gives real routing conditions: exactly one of `url` or `uploadId`, with uploadId explicitly tied to the upload_file sibling. It also tells the agent when to switch modes ('send the file as a `document` to deliver it untouched'). It does not, however, contrast itself with sibling senders like send_text or explain when a reply is preferable (reply_to_message vs the replyToMessageId parameter).

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