Skip to main content
Glama

browser_wait_for_download

browser_wait_for_download
Read-only

Waits for a browser download to complete or fail, optionally scoped to a specific tab, so an agent can continue only after the file transfer finishes.

Instructions

Wait for a download to complete or fail, optionally only one started from a given tab.

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_wait_for_download"
  }
}

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.
timeout_msNo
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that — the wait terminates on either success or failure, and the observation can be narrowed to a tab. It omits what happens on timeout (error vs. returning a pending state) and whether the call blocks until resolution.

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

Conciseness4/5

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

A single compact sentence with the resource and the tab-scoping qualifier front-loaded and no filler. Brevity is achieved at some cost to completeness, but nothing in the text is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return semantics, and it does not say whether the result is the completed download record, a status, or an error on timeout. For a blocking wait with a timeout parameter and no required arguments, the agent lacks the information needed to interpret the outcome.

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 75% and tab_id, session_id and session_name are well documented in the schema, so the baseline of 3 applies. The one undocumented parameter, timeout_ms, is also untouched by the description — no default value or expiry behavior is given — which is the most consequential gap for a waiting tool.

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 gives a specific verb and resource ("Wait for a download to complete or fail") and adds a scoping qualifier ("optionally only one started from a given tab"), which clearly separates it from sibling wait tools such as browser_wait_for_element. It stops short of naming the alternative it complements (e.g., browser_list_downloads) for checking non-blocking state.

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

Usage Guidelines2/5

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

It says what the tool does but not when to reach for it: no guidance on using it after triggering a click that starts a download, no mention of browser_list_downloads as the non-blocking alternative, and no note on prerequisites (claimed tab, session). Usage is only inferable from the verb "Wait".

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