Skip to main content
Glama

Argoshot

Save a web page as PDF

page_to_pdf
Read-onlyIdempotent

Renders a public page to a PDF and returns a link to the file (kept about 4 hours; PDFs are not shown inline). Each render counts against the account's plan.

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": {
      "url": "<url>"
    },
    "name": "page_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic address of the page
paperNoPaper size, like a4 or letter
marginNoMargin on every side, like 10mm
optionsNo
landscapeNo
wait_untilNo
print_backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses three behaviors an agent could not otherwise know: the returned link expires after about 4 hours, PDFs are not rendered inline, and each render is metered against the account's plan. Those are exactly the retention, output-handling, and billing facts that affect whether and how an agent calls this.

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 first and the operational caveats (retention, inline behavior, metering) packed into a single parenthetical. Nothing is repeated from the title and nothing could be cut without losing information.

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?

It correctly fills the gap left by the absent output schema by describing the return value as a link with a TTL. However, with 7 parameters, a nested object, and only 43% schema coverage, the definition leaves the rendering options opaque, so it is only partially adequate for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 43% across 7 parameters, including a nested free-form "options" object and an enum for wait_until, so the description needs to compensate and does not. The only parameter-adjacent fact is that the URL must be public; nothing is said about paper, margin, landscape, print_background, or wait_until.

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?

"Renders a public page to a PDF and returns a link to the file" gives a specific verb and resource plus the return shape, which distinguishes it from page_to_markdown and screenshot_url by output type. It never explicitly names a sibling or states the contrast, so it stops short of a 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?

The word "public" implies a precondition (no authenticated or private pages), and the quota sentence hints at cost-awareness, but neither is framed as a when-to-use rule. There is no explicit guidance on choosing this over page_to_markdown or screenshot_url, so usage is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources