Render the current browser page as a PDF document using a session ID, with options for scale, landscape orientation, and background graphics.
Render the current page as a PDF document.
| Name | Required | Description | Default |
|---|---|---|---|
| scale | No | Page scale factor (default 1) | |
| landscape | No | Landscape orientation (default false) | |
| session_id | Yes | Session ID returned by browser_navigate | |
| print_background | No | Print background graphics (default false) |
Changes observed during successful MCP inspections.
v2.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it doesn't say whether the PDF is returned inline, saved to a path, or downloaded, which is the key behavioral question for a generation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. It is efficient, though the brevity contributes to the missing usage and output information rather than being purely a virtue.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
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 explain how the generated PDF is delivered (bytes, URL, file path, download). It omits this entirely, leaving a real gap for an agent that must consume the result.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so scale, landscape, print_background, and session_id are fully documented in the schema with defaults. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Render) and resource (current page as a PDF document), which is unambiguous. It does not differentiate from the closest sibling, browser_screenshot, which also captures the current page but to an image.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose PDF rendering over browser_screenshot, scrape, or extract, nor any noted prerequisites. The agent must infer the use case entirely from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.