Skip to main content
Glama

List observed download events

browser_list_download_events
Read-only

Retrieve buffered Firefox download events from the current connection to see when downloads start, finish, or fail, complementing directory-based download listings.

Instructions

Report the download events the browser pushed since this server connected (browsingContext.downloadWillBegin / downloadEnd). Complements browser_list_downloads: the directory shows the RESULT, these events show WHEN a download started, finished, or failed. Events are buffered in memory (most recent 500) and only cover the lifetime of this connection.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax entries, newest first (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds critical operational constraints the agent could not otherwise know: events are buffered in memory, capped at the most recent 500, and only cover the lifetime of this connection. That retention/lifetime scoping materially changes how the agent should interpret empty or partial results.

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?

Three tight sentences: what it reports first, then the sibling contrast, then the buffering caveat. No filler, and the most decision-relevant information is front-loaded.

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 should ideally hint at the shape of returned entries (fields of a downloadWillBegin/downloadEnd record) beyond the event names. Otherwise it is complete: source, scope, limits, and sibling distinction are all covered for a simple one-parameter read tool.

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 limit parameter already documents 'max entries, newest first (default 20)' with a max of 200. The description mentions the 500-entry buffer but does not tie it to the limit parameter or clarify ordering semantics beyond what the schema states, so baseline 3 applies.

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 a specific verb and resource ('Report the download events the browser pushed since this server connected') and even names the underlying protocol events (downloadWillBegin / downloadEnd). It explicitly distinguishes itself from the nearest sibling, browser_list_downloads, so an agent can pick correctly without opening either 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?

Names the alternative and the exact condition that selects it: 'the directory shows the RESULT, these events show WHEN a download started, finished, or failed.' That is a concrete routing rule, not an implied one.

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