Skip to main content
Glama

Perisclaw: Use ChatGPT and Claude with your WhatsApp

Download Media

media_download
Read-only

Fetch the photo, voice note, video or document attached to a message in the user's own WhatsApp so it can be viewed or described here. Use it only for a message the user is asking about. Pass that message's message_id. Files up to 10 MB are shown here; larger files can't be opened in this chat.

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": "media_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYesId of the message whose media to download.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, non-destructive behavior, and open-world access. The description adds meaningful context beyond that: the media is limited to the user's own WhatsApp, should only be fetched for a message the user is discussing, and files larger than 10 MB cannot be opened here.

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?

The description is three tightly written sentences: purpose first, usage restriction second, size limitation third. Each sentence contributes necessary information and nothing is redundant.

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

Completeness5/5

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

Given a single required parameter, full schema coverage, and annotations covering safety, the description supplies everything an agent needs: what the tool fetches, when to use it, which ID to pass, and the practical 10 MB limit. No output schema exists, so return-value explanation is not required.

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 only parameter, message_id, is already fully documented. The description reinforces that the agent should pass the message_id of the message in question, but adds no syntax or format details beyond the schema.

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 ('Fetch') and a concrete resource ('photo, voice note, video or document attached to a message'), making clear exactly what the tool returns. It also scopes the resource to the user's own WhatsApp, which distinguishes it from broader message-search or chat-listing tools.

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?

It gives a clear usage condition: 'Use it only for a message the user is asking about,' and instructs the agent to pass that message's message_id. It does not name a specific alternative tool for other media-related cases, but the restriction is explicit and sufficient for correct invocation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.