Skip to main content
Glama

list_downloads

Read-only

Lists files downloaded by a browser instance, oldest first, with URL, filename, path, state, sizes, and tab ID; also reports the download directory so you can locate completed files.

Instructions

Lists the files the instance's pages downloaded, oldest first (id, url, file_name, path once complete, state: in_progress, completed or canceled, sizes, tab_id), and their directory (a folder of --downloads-dir named after the instance id, else the instance's temporary profile, deleted with it). An action that starts a download also says where the file went.

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

Input Schema

NameRequiredDescriptionDefault
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already marks this as a safe read, and the description adds substantial context beyond that: ordering (oldest first), the three-value state model, and how path resolution works (a folder under --downloads-dir named after the instance id, otherwise the instance's temporary profile which is deleted with it). That directory/deletion detail is genuinely useful behavioral information not derivable from annotations. It omits any note on result limits or what happens when no downloads exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the body is a single dense run-on sentence built from nested parentheticals (state values, directory rules, deletion behavior), which makes it harder to parse than necessary. Every piece of information earns its place, but the structure could be split into two or three sentences for scanability.

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?

With no output schema, the description appropriately takes on the burden of describing the return shape: fields, ordering, state enum values, and file location semantics. For a one-parameter read-only list tool this covers what an agent needs to call and interpret it. The only gaps are pagination/limits and empty-result behavior.

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% and the single parameter instance_id is documented in the schema with its default, so the schema carries the parameter burden. The description reinforces the instance scoping through the directory-resolution explanation ('a folder of --downloads-dir named after the instance id'), but adds no new syntax or format detail for the parameter itself. Baseline 3 is appropriate.

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 and resource ('Lists the files the instance's pages downloaded') and adds a concrete scope ('oldest first'). It goes further by enumerating the returned fields (id, url, file_name, path, state, sizes, tab_id), so an agent knows exactly what this returns without opening a schema. It does not explicitly contrast itself with sibling list tools such as list_tabs or list_instances, which keeps it just short of 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 only implied: an agent can infer this is the way to inspect download activity for an instance, and the mention that 'an action that starts a download also says where the file went' hints at cross-tool linkage. There is no explicit when-to-use, when-not-to-use, or named alternative, so guidance is minimal but not absent.

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