Skip to main content
Glama

save_media

Downloads media from a list_media item or URL to disk under ~/.tether/media// with browser cookies, handling blobs, data URLs, canvases, and HLS/DASH streams. Returns the saved path.

Instructions

Save an item from list_media (or any URL) to disk under ~/.tether/media//, using the browser's cookies. Handles normal files, blob: and data: URLs, canvases, and HLS/DASH streams (through ffmpeg). Returns the file path.

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

Input Schema

NameRequiredDescriptionDefault
idNoId from list_media, e.g. m3.
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
urlNo
filenameNo
timeout_secondsNoDefault 900, for long streams.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and does well: it discloses the on-disk destination, that browser cookies are reused for authenticated fetches, that ffmpeg is required for streams, and that the file path is returned. It omits overwrite behavior when the target file exists and any error/failure semantics.

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 dense sentences, front-loaded with the action and destination, then capability coverage, then the return value. No filler or restated name.

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?

For a 5-parameter tool with no output schema, it covers source, destination, supported media types, dependency, and return value. What remains missing is failure behavior and filename/overwrite semantics, which matters for a disk-writing tool.

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 60% with id, tab and timeout_seconds documented in the schema; the description adds only that url accepts arbitrary sources. filename and timeout_seconds semantics (naming, collision handling, the 900s default for long streams) are not enriched beyond the bare schema defaults.

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 (save) and resource (an item from list_media or any URL), plus the destination path pattern ~/.tether/media/<site>/. It also names list_media as the primary source, but never distinguishes itself from the sibling download_file, leaving a real overlap unresolved.

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?

Implies when to use it by pointing at list_media items, raw URLs, blob:/data: URLs, canvases and HLS/DASH streams, so an agent can infer eligibility. However there is no explicit when-not guidance and no comparison to download_file, which sounds like it could handle similar work.

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