Meta Cloud API MCP Server

download_media

Download media content from a WhatsApp media URL and save it to a local file path. Obtain the URL using get_media_info before downloading.

Instructions

Download media content from a WhatsApp media URL. Use get_media_info first to obtain the URL.

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

Input Schema

Name	Required	Description	Default
`media_url`	Yes	The media download URL (obtained from get_media_info)
`save_path`	Yes	Absolute file path to save the downloaded media

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the core action and the prerequisite, but does not disclose potential side effects (e.g., file overwriting, access token requirements, error behavior, or return format). This is a minimal disclosure for a tool with no annotation safety net.

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 concise sentences, front-loaded with the action and a clear prerequisite. Every word earns its place with no redundancy or filler.

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?

Given the low complexity (2 params, no output schema) and clear schema, the description is minimally viable. However, it lacks information about return values, error handling, or expected behavior after download, which would be useful for a tool without annotations or output schema. It is adequate but not 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%, with both parameters clearly described (media_url and save_path). The description adds no additional semantic information beyond the schema, so it meets the baseline but does not enhance parameter understanding.

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 clearly states the specific action (download media content) and the resource (a WhatsApp media URL), distinguishing it from siblings like upload_media and get_media_info. It is not a tautology and provides clear scope.

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?

The description explicitly instructs to use get_media_info first to obtain the URL, giving clear usage context and a prerequisite. It does not explicitly mention when not to use it, but the prerequisite guidance is strong and implies the intended workflow.

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