Skip to main content
Glama

set_download_behavior

Configures Firefox download handling to save automatically to a specified folder, cancel downloads, or reset to browser default, avoiding the native save-file dialog.

Instructions

Control how downloads are handled: allow (save to a destination folder), deny (cancel), or reset to default. Avoids the native save-file dialog. Requires a recent Firefox.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "behavior": "<behavior>"
    },
    "name": "set_download_behavior"
  }
}

Input Schema

NameRequiredDescriptionDefault
behaviorYes'allowed' saves downloads to `downloadFolder`, 'denied' cancels them, 'default' resets to the browser default
downloadFolderNoPath to the folder where downloads should be stored, created if missing. Only used for behavior='allowed', where it defaults to ~/.firefox-mcp/output/downloads. Relative paths resolve against the current working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / downloadFolder / description
      Previous value: -"Path to the folder where downloads should be stored, created if missing. Only used for behavior='allowed', where it defaults to ~/.firefox-devtools-mcp/output/downloads. Relative paths resolve against the current working directory."New value: +"Path to the folder where downloads should be stored, created if missing. Only used for behavior='allowed', where it defaults to ~/.firefox-mcp/output/downloads. Relative paths resolve against the current working directory."
  2. Changed2 schema fields changedv0.10.3
    • changedInput schema / properties / behavior / description
      Previous value: -"'allowed' saves downloads automatically, 'denied' cancels them, 'default' resets to the browser default"New value: +"'allowed' saves downloads to `downloadFolder`, 'denied' cancels them, 'default' resets to the browser default"
    • addedInput schema / properties / downloadFolder
      Added value: +{
      +  "description": "Path to the folder where downloads should be stored, created if missing. Only used for behavior='allowed', where it defaults to ~/.firefox-devtools-mcp/output/downloads. Relative paths resolve against the current working directory.",
      +  "type": "string"
      +}
  3. Addedv0.9.15

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful traits: the three modes' effects, that it bypasses the native save-file dialog, and a version prerequisite. It omits important behavior such as whether the setting persists across sessions, whether it applies to in-flight downloads, or what happens if the setting cannot be applied.

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?

Three short sentences with the core action front-loaded and no filler; the mode enumeration is compact and the version caveat is placed at the end where it is easy to scan. Slight redundancy between the parenthetical mode glosses and the schema's own enum descriptions.

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?

For a two-parameter configuration tool with no output schema and no annotations, the description covers the modes, the dialog-avoidance side effect, and the browser prerequisite. Missing only persistence/session-scope detail, which is a minor gap at this complexity level.

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 adds a bit by restating the mode semantics in prose ('allow (save to a destination folder)', 'deny (cancel)', 'reset to default'). downloadFolder is left entirely to the schema, which documents it thoroughly, so no real gap exists.

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 names a specific verb+resource ('Control how downloads are handled') and enumerates all three modes (allow/deny/reset), so an agent can tell what the tool does immediately. It doesn't explicitly differentiate itself from siblings like list_downloads or clear_downloads, which keeps it at 4 rather than 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 implied rather than stated: the mention of avoiding the native save-file dialog and requiring a recent Firefox gives context for when it is applicable, but there is no explicit when-to-use/when-not guidance or pointer to alternatives such as list_downloads or clear_downloads.

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