Skip to main content
Glama
whatsapp-mcp

whatsapp-mcp

by petrkyncl

download_media

Download a WhatsApp message's attached file and display its content: images, video frames, or extracted text from PDF, Word, Excel, CSV and TXT; also returns the original file location.

Instructions

Download the file of a WhatsApp message (photo, video, voice note, sticker, document: PDF, Word, Excel, CSV, TXT…) and show its content: pictures as images, frames of a video, text of PDF/Word/Excel/CSV/TXT. Also returns where the original file is. message_id comes from list_messages (messages with file: true).

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": {
      "message_id": "<message_id>"
    },
    "name": "download_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatNo
message_idYes

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?

With no annotations, the description carries the full burden and does disclose non-obvious behavior: it renders content by type (images as images, video frames, extracted text) and separately returns the original file location. It omits operational traits an agent would want — download size/latency limits, permission requirements, and error behavior for unsupported or 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.

Conciseness4/5

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

Two sentences, front-loaded with the action and return behavior, followed by the ID sourcing note. The parenthetical file-type list is longer than needed but does set expectations about supported formats, so it largely earns its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description does a fair job of explaining what comes back (rendered content plus file location), which is the main gap it needed to fill. It is still incomplete for a file-handling tool: the `chat` parameter is undocumented and there is no mention of size limits, unsupported types, or failure modes.

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 0%, so the description must compensate; it covers message_id well (source tool and the file: true filter) but leaves the `chat` parameter entirely unexplained — its format, whether it is required in practice, or how it interacts with message_id. One of two parameters is effectively undocumented.

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 ("Download the file of a WhatsApp message") and enumerates the media kinds it handles, plus what it returns. It also names the sibling (list_messages) that produces the required ID, so an agent can place it in a workflow without opening other schemas.

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 a concrete precondition: message_id must come from list_messages and the target message must have file: true, which effectively tells the agent when this tool applies rather than other message tools. It stops short of explicit exclusions (e.g., what to do for text-only messages or very large files) or naming a fallback tool.

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