Skip to main content
Glama
Sign In
Chrome Bridge

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

manage_downloads

List downloads, start one, or wait for the newest to finish. Files land in the browser Downloads folder, not on the server.

Instructions

List downloads, start one, or wait for the newest to finish. Files land in the browser Downloads folder, not on the server. download reports the real state: with Chrome set to ask where to save, it comes back waiting_for_user — bytes fetched, nothing moves until someone picks a destination. To save a file that has a URL use http_request with save_to instead: browser cookies, bytes on disk, no dialog; a file the page builds goes through capture_downloads.

Input Schema

NameRequiredDescriptionDefault
urlNoWhat to download (action=download); sent with the session cookies of its origin
limitNoMax download entries returned, newest first
actionYesdownload fetches with the browser cookies and reports the real state; wait_for_complete blocks until the newest finishes
timeoutNoMax ms (wait_for_complete)
filenameNoRelative path inside the Downloads folder (action=download)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • changedInput schema / properties / action / description
      Previous value: -"download fetches with the browser cookie jar and reports the real state; wait_for_complete blocks until the newest finishes"New value: +"download fetches with the browser cookies and reports the real state; wait_for_complete blocks until the newest finishes"
  2. Changed4 schema fields changedv1.15.0
    • changedInput schema / properties / action / description
      Previous value: -"wait_for_complete blocks until the newest download finishes or times out"New value: +"download fetches with the browser cookie jar and reports the real state; wait_for_complete blocks until the newest finishes"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "wait_for_complete"
-]New value: +[
+  "list",
+  "wait_for_complete",
+  "download"
+]
    • addedInput schema / properties / filename
      Added value: +{
+  "description": "Relative path inside the Downloads folder (action=download)",
+  "type": "string"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "What to download (action=download); sent with the session cookies of its origin",
+  "type": "string"
+}
  3. Changed2 schema fields changedv1.10.0
    • addedInput schema / properties / action / description
      Added value: +"wait_for_complete blocks until the newest download finishes or times out"
    • addedInput schema / properties / limit / description
      Added value: +"Max download entries returned, newest first"
  4. First observedv1.8.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds substantial context beyond them: files land in the browser Downloads folder not on the server, and 'download' reports the real state, returning waiting_for_user with bytes fetched but nothing moved when Chrome asks where to save.

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?

Front-loaded with the three actions, then the storage location, then the state semantics, then the sibling routing. Dense but every sentence carries distinct, load-bearing information with no filler.

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?

No output schema exists, yet the description explains the meaningful return state (waiting_for_user) for the download action. Annotations carry the safety profile. Minor gap: it doesn't characterize what 'list' returns or key entries, but the essential call-correctness information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all five parameters (baseline 3). The description adds meaning beyond it by explaining what each action does behaviorally, particularly 'download' fetching with browser cookies and reporting the true state with the waiting_for_user nuance.

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?

States three specific verbs (list, start/download, wait) against the resource 'downloads', and immediately names the sibling tools it is not (http_request with save_to, capture_downloads). An agent can distinguish this from those siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing rules: use http_request with save_to for a file that has a URL, and capture_downloads for a file the page builds. Both the alternative and the condition selecting it are spelled out, leaving nothing to inference.

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