Skip to main content
Glama
getscreenshot-mcp

getscreenshot-mcp

Official
by rasterwise

Capture PDF

capture_pdf
Read-only

Save a public web page as an A4 PDF and get a link to keep, share, or archive.

Instructions

Save a public web page as an A4 PDF and return a link to the file. Use it when the user wants a document to keep, share or archive. The PDF is not shown to you; to look at a page use capture_screenshot. Costs 1 screenshot of the monthly quota per call, failed captures included. Takes about 9-25 seconds. The link is public to anyone who has it and expires in 30 days. Limits: the page must be reachable from the public internet (no localhost or private networks).

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the page, reachable from the public internet. localhost and private-network addresses cannot be captured; use render_html for local HTML.
wait_msNoExtra wait in milliseconds after load, before the capture. API default 2000. Raise it for late animations or client-side rendering.
custom_cssNoCSS injected before the PDF is made, for example print tweaks.
wait_untilNoWhen the page counts as loaded. API default "networkidle2". Use "domcontentloaded" for heavy or slow sites (fastest, most reliable); "networkidle0" waits for all network activity to stop.
hide_selectorsNoCSS selector(s) to hide (display:none) before capture, comma-separated, for example ".newsletter-popup, #ad-banner".

Output Schema

NameRequiredDescriptionDefault
pdf_urlYesThe PDF file. Public to anyone who has the link.
warningsYes
origin_urlYes
captured_atYes
page_statusYes
expires_in_daysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses quota cost (1 screenshot per call, failed captures included), latency (9-25 seconds), link publicity and 30-day expiry, and the public-internet reachability constraint. These are exactly the operational facts the readOnly/openWorld hints do not convey.

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?

Six short sentences, front-loaded with purpose and routing, then cost, latency, link lifetime and limits in descending order of importance. No filler; each sentence carries a distinct fact an agent needs before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a capture tool with an output schema, the description covers purpose, cost, timing, link lifecycle and input constraints. Nothing needed to invoke it correctly or set expectations is missing.

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 coverage is 100%, so every parameter is already documented in the input schema, which sets the baseline at 3. The description only reinforces the URL reachability rule and adds nothing for wait_ms, custom_css, hide_selectors or wait_until beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource plus output: "Save a public web page as an A4 PDF and return a link to the file." It explicitly distinguishes itself from capture_screenshot, so an agent can route correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the use case ("when the user wants a document to keep, share or archive") and names the alternative for the opposite need ("to look at a page use capture_screenshot"). The schema further routes local HTML to render_html, giving explicit when/when-not coverage.

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