Skip to main content
Glama

screenshot_page

Read-only

Capture Firefox page screenshots as PNG data or files, choosing the current viewport or full scrollable document for visual testing and documentation.

Instructions

Capture viewport screenshot as base64 PNG. Set fullPage for the whole scrollable document.

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

Input Schema

NameRequiredDescriptionDefault
saveToNoSave the screenshot to a file instead of returning it as image data in the response. Pass a file path, an existing directory (generated file inside), or true (generated file under ~/.firefox-mcp/output/). Relative paths resolve against the current working directory.
fullPageNoCapture the whole scrollable document (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / saveTo / description
      Previous value: -"Save the screenshot to a file instead of returning it as image data in the response. Pass a file path, an existing directory (generated file inside), or true (generated file under ~/.firefox-devtools-mcp/output/). Relative paths resolve against the current working directory."New value: +"Save the screenshot to a file instead of returning it as image data in the response. Pass a file path, an existing directory (generated file inside), or true (generated file under ~/.firefox-mcp/output/). Relative paths resolve against the current working directory."
  2. Changed1 schema field changedv0.10.3
    • addedInput schema / properties / fullPage
      Added value: +{
      +  "description": "Capture the whole scrollable document (default: false)",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changedv0.9.15
    • changedInput schema / properties / saveTo / description
      Previous value: -"Optional file path to save the screenshot to instead of returning it as image data in the response."New value: +"Save the screenshot to a file instead of returning it as image data in the response. Pass a file path, an existing directory (generated file inside), or true (generated file under ~/.firefox-devtools-mcp/output/). Relative paths resolve against the current working directory."
    • changedInput schema / properties / saveTo / type
      Previous value: -"string"New value: +[
      +  "boolean",
      +  "string"
      +]
  4. Changed1 schema field changedv0.9.3
    • addedInput schema / properties / saveTo
      Added value: +{
      +  "description": "Optional file path to save the screenshot to instead of returning it as image data in the response.",
      +  "type": "string"
      +}
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already establishes this is a safe read, and the description usefully adds the output format (base64 PNG) and the default viewport scope versus full scrollable document. It does not mention that supplying saveTo suppresses the inline image data, nor which page is captured, leaving meaningful behavioral gaps.

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?

Two short, front-loaded sentences with no filler; the capture format leads and the option follows. Minor redundancy with the schema documentation of fullPage is the only inefficiency.

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?

The tool is simple (2 optional params, no output schema), and the description covers format and the main option. It is silent on scope — which page/frame is captured — and on the saveTo branch that changes the response shape, so it is adequate but not complete.

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 description coverage is 100% and both parameters are fully documented in the schema, so the baseline is 3. The description's 'Set fullPage...' merely restates the schema's fullPage description and says nothing about saveTo's path-resolution behavior, which the schema already covers.

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?

A concrete verb and resource — 'Capture viewport screenshot as base64 PNG' — tells an agent exactly what it gets back. It stops short of distinguishing itself from the sibling screenshot_by_uid (element-level capture) or print_page, so an agent must infer the difference from names alone.

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?

The description never states when to prefer this tool over screenshot_by_uid, print_page, or screencast_start, nor any preconditions (e.g., an open page). The second sentence about fullPage is a parameter hint, not usage guidance.

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