Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Download media from a WhatsApp message

download_media
Read-onlyIdempotent

Download media attached to a WhatsApp message and save it to disk on the MCP server. Images under 1 MB are returned inline; fails if media expired.

Instructions

Download the photo/video/audio/document attached to a message and save it to disk on the machine running wazap. Images of 1 MB or less are also returned inline so you can look at them.

Fails with MEDIA_UNAVAILABLE when WhatsApp has expired the file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
save_toNoAbsolute directory to save into (default: <data-dir>/media)
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
message_idYesA message with has_media=true

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses a filesystem side effect (writes to disk on the host), the inline-return behavior for images ≤1 MB, and the specific error code MEDIA_UNAVAILABLE for expired media.

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 what is downloaded and where, followed by the inline-image nuance and the failure mode. No filler, no repetition of the name or title.

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?

There is no output schema, yet the description covers the practical return behavior (file on disk, inline image for small files) and the key failure mode. A brief note on the returned path/format and whether existing files are overwritten would make it fully complete.

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 message_id, save_to, and account_id are already fully documented in the schema, including the default save directory. The description adds no syntax, format, or constraint detail beyond that, so the baseline 3 applies.

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 (download) and resource (photo/video/audio/document attached to a message) plus the destination (save to disk on the wazap host). An agent can distinguish this from read_messages, get_message, or transcribe_audio without opening a schema.

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?

Usage is implied by the purpose (you call this when you need the actual file for a message). There is no explicit when-to-use vs alternatives guidance, e.g. it never says to use this instead of transcribe_audio for audio or that the message must have has_media=true. The MEDIA_UNAVAILABLE note is a failure condition, not routing guidance.

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