Skip to main content
Glama

web_download_pdf

Saves the current Chrome page or specified tab as a PDF and returns its file path, letting you choose a file or folder destination.

Instructions

Save the current page as a PDF and return the file path. Optional 'path' (a file or a folder); defaults to ~/Downloads named after the page title.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose the return value (file path) and the default destination/naming (~/Downloads, named after page title), which is genuinely useful, but it says nothing about overwrite behavior when 'path' points at an existing file, whether the page must be fully loaded first, or what happens on failure. For a filesystem-writing tool with zero annotation coverage, that is a real gap.

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 tight sentences, zero filler, with the action and the return value front-loaded before the parameter detail. Every clause carries information the agent needs.

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, zero-required tool this is nearly complete: the action, the return value, and the default path resolution are all covered, and target_id is handled by the schema. The only shortfall is the absence of any note on overwriting existing files or error behavior, which matters for a tool that writes to disk.

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 50%: target_id is documented in the schema, but 'path' has no schema description at all. The description compensates well by explaining that 'path' may be either a file or a folder and that omitting it defaults to ~/Downloads with a page-title-derived name — semantics the schema does not provide.

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?

States a specific verb and resource: 'Save the current page as a PDF and return the file path.' That is concrete enough to act on, but it never distinguishes itself from the nearest sibling, web_screenshot (image capture) or web_html (markup capture), leaving the agent to infer why PDF is the right choice.

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 'save as PDF' — there is no explicit when-to-use or when-not-to-use statement, and no mention of the sibling capture tools it competes with. An agent can guess the context (archiving a rendered page), but the definition never says so.

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