Skip to main content
Glama

download_media

Read-only

Save images, voice, video, or files from a QQ message or direct URL to the server and return the local path for other tools to send or post.

Instructions

Save the image/voice/video/file of a message (or any URL) on the server and return its local path, which other tools (send_file, send_qzone_msg images…) accept.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "download_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoOr a direct URL
nameNoFile name to save as
indexNoWhich media segment (0-based)
message_idNoMessage with the media

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false. The description adds genuine context beyond them: the media is written to server storage and a local path is produced, which is the tool's main side effect and the key fact an agent needs. There is a mild tension with readOnlyHint since a file is materialized on disk, but this reads as local caching of remote content rather than mutation of service data; no permissions, failure modes, or overwrite behavior are described.

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?

A single sentence that front-loads the action, then the return value, then the downstream consumers. Dense but readable, with no filler; the parenthetical example list is slightly loose but earns its place by naming concrete consumers.

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, and the description correctly compensates by stating the return value is a local path accepted by other tools. For a four-parameter, all-optional download tool that is sufficient; only error cases (media absent, index out of range, URL unreachable) and the url-vs-message_id precedence are left uncovered.

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 coverage is 100%, so all four parameters are already documented in the schema. The description adds only that a message media source and a direct URL are alternatives, without stating whether they are mutually exclusive or how index interacts with message_id. Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: save the image/voice/video/file of a message or any URL on the server, and return the local path. The scope (media of a message, or arbitrary URL) is concrete enough for an agent to know exactly what it gets back. It does not explicitly differentiate itself from the many download_file* siblings, which keeps it from a 5.

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 rather than stated: the description notes the returned path is accepted by send_file and send_qzone_msg, which tells the agent when this tool is a prerequisite. There is no explicit when-not guidance and no routing away from download_file/download_file_stream siblings, so the agent must infer the choice.

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