Skip to main content
Glama

print_page

Read-only

Converts the current page into a PDF using print CSS, saves it to a chosen path or default output folder, and returns the saved file path.

Instructions

Print the current page to a PDF file using print CSS. Returns the saved file path.

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

Input Schema

NameRequiredDescriptionDefault
saveToNoWhere to save the PDF. Pass a file path, an existing directory (generated file inside), or true or omit it (generated file under ~/.firefox-mcp/output/). Relative paths resolve against the current working directory.
landscapeNoUse landscape orientation (default: false)
backgroundNoPrint background colors and images (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • changedInput schema / properties / saveTo / description
      Previous value: -"Where to save the PDF. Pass a file path, an existing directory (generated file inside), or true or omit it (generated file under ~/.firefox-devtools-mcp/output/). Relative paths resolve against the current working directory."New value: +"Where to save the PDF. Pass a file path, an existing directory (generated file inside), or true or omit it (generated file under ~/.firefox-mcp/output/). Relative paths resolve against the current working directory."
  2. Addedv0.10.6

TDQS

A3.6/5.0
Behavior3/5

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

The description adds real context beyond readOnlyHint=true by disclosing that rendering uses print CSS and that a file is written and its path returned, which the annotations do not convey. It is silent on failure behavior, whether rendering waits for the page to settle, and whether the call blocks, and it sits in mild tension with readOnlyHint since a PDF is persisted to disk (though page state is not mutated).

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 sentences, zero filler, with the core action front-loaded and the return value immediately after. Nothing could be removed without losing information.

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 three-parameter tool with full schema coverage and no output schema, the definition covers purpose, mechanism (print CSS), and the return value. Only edge-case behavior on navigation failures or blocking is unaddressed, which is a minor gap for a tool of this simplicity.

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%: saveTo's path/directory/true/omit semantics, the default output directory, and relative-path resolution are all documented in the schema, as are landscape and background defaults. The description contributes no additional parameter meaning, so the baseline 3 applies.

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?

"Print the current page to a PDF file using print CSS" names a specific verb, target resource, and output format, which lets an agent separate it from screenshot_page (image capture) and get_page_text. It stops short of naming any sibling explicitly, so the differentiation is inferable rather than stated.

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 only implied by the verb "print" and the "using print CSS" qualifier; there is no explicit statement of when to prefer this over screenshot_page, nor any prerequisite or exclusion. An agent can guess the intent, but the definition does no routing work.

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