Skip to main content
Glama

browser_list_downloads

browser_list_downloads
Read-onlyIdempotent

Lists recent Chrome downloads and shows whether a tab is associated, helping agents verify completed file saves. Use it to inspect download history when tracking browser activity.

Instructions

List recent Chrome downloads. Chrome does not record which tab started a download, so tab_id is null unless a previous browser_wait_for_download associated it.

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

Input Schema

NameRequiredDescriptionDefault
tab_idNoChrome tab ID. Defaults to the active tab when omitted.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

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?

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description earns credit by adding a genuine behavioral caveat: Chrome does not record the originating tab, so tab_id comes back null unless browser_wait_for_download ran first. That is context the annotations cannot supply.

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?

Two tight sentences, front-loaded with the purpose and followed by the one caveat that matters. No filler or restated field documentation.

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?

With no output schema, the description must carry the return-value burden. It says 'recent' downloads but never defines the window, result limits, or the fields returned (filename, path, state). Adequate but incomplete for a listing tool without a structured output contract.

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 baseline is 3. The description goes beyond the schema by explaining the meaning of tab_id in results — null unless a prior browser_wait_for_download associated it — which the schema's 'Defaults to the active tab' note does not cover.

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?

The description opens with a specific verb and resource: "List recent Chrome downloads." That is unambiguous and distinguishable from browser_wait_for_download, which is named later as the tool that associates a tab. It stops short of an explicit contrast, but the resource is clear.

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 note that tab_id is null unless a previous browser_wait_for_download associated it functions as a workflow hint, but there is no explicit when-to-use or when-not-to-use statement and no guidance on choosing this over browsing history or other listing tools.

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