Skip to main content
Glama

download_file

Downloads a URL through your browser using your cookies, then returns the saved file’s path; restricted to shared-tab sites unless bypass mode is enabled.

Instructions

Download a URL through the user's browser, with their cookies, and get the saved file's path. Limited to sites of shared tabs unless bypass mode is on.

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": {
      "url": "<url>"
    },
    "name": "download_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoTab handle from list_tabs, e.g. "chrome:812". Optional when only one tab is shared.
urlYes
browserNo
filenameNoFile name inside the browser's download folder.

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?

With no annotations, the description does useful work: it discloses that the download runs in the user's authenticated browser with their cookies, that it returns a saved file path, and that shared-tab site scoping applies unless bypass mode is enabled. It omits whether the call blocks until the download finishes or returns immediately (relevant given the wait_for_download sibling), and says nothing about timeouts or failure behavior on restricted sites.

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?

One sentence, front-loaded with the action and mechanism, then the return value, then the scope restriction. No filler and nothing that could be trimmed without losing information.

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?

For a 4-parameter tool with no annotations and no output schema, the description covers mechanism, return value, and scoping, which is a reasonable core. It leaves out the sync/async question and the coordination with the download-related siblings, which are the main things an agent could get wrong.

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 50%: tab and filename are documented in the schema, while url and browser are not. The description indirectly motivates the tab parameter via the shared-tab scoping rule and implies the browser parameter via "the user's browser," but adds no meaning for url or for how browser and tab relate. Baseline 3 fits.

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?

"Download a URL through the user's browser, with their cookies, and get the saved file's path" is a concrete verb+resource with an unusual mechanism (user's browser session) called out. It separates it from a server-side fetch or from upload_file/list_downloads, though it never names a sibling explicitly.

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?

The constraint "Limited to sites of shared tabs unless bypass mode is on" is real usage guidance and hints at the request_bypass route when the constraint blocks you. However there is no explicit when-to-use vs. alternatives, and no mention of wait_for_download or list_downloads, which an agent must coordinate with after the call.

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