Hydrafetch

Screenshot

screenshot

Render a page in a real browser and capture a PNG, returning its public URL. Use when the question is what the page looks like rather than what it says.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The URL to capture.
`maxAge`	No	Reuse a stored screenshot younger than this many milliseconds. Defaults to 7 days, so a repeat returns the stored PNG without re-rendering and without applying waitFor. Pass 0 to force a fresh capture.
`timeout`	No	Overall time budget for the capture, in milliseconds.
`waitFor`	No	Extra milliseconds to let the page settle before capture.
`fullPage`	No	Capture the whole scrollable page rather than the viewport.
`viewport`	No	Screen size to render at. Defaults to desktop (1920x1080). Ignored when width or height are given.
`viewportWidth`	No	Exact viewport width in pixels. Overrides viewport.
`viewportHeight`	No	Exact viewport height in pixels. Overrides viewport. With fullPage the capture still extends to the full page height.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedAug 31, 2026

addedInput schema / properties / maxAge

Added value: +{
+  "description": "Reuse a stored screenshot younger than this many milliseconds. Defaults to 7 days, so a repeat returns the stored PNG without re-rendering and without applying waitFor. Pass 0 to force a fresh capture.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / timeout

Added value: +{
+  "description": "Overall time budget for the capture, in milliseconds.",
+  "maximum": 120000,
+  "minimum": 1000,
+  "type": "integer"
+}

addedInput schema / properties / viewport

Added value: +{
+  "description": "Screen size to render at. Defaults to desktop (1920x1080). Ignored when width or height are given.",
+  "enum": [
+    "desktop",
+    "laptop",
+    "tablet",
+    "mobile"
+  ],
+  "type": "string"
+}

addedInput schema / properties / viewportHeight

Added value: +{
+  "description": "Exact viewport height in pixels. Overrides viewport. With fullPage the capture still extends to the full page height.",
+  "maximum": 2160,
+  "minimum": 240,
+  "type": "integer"
+}

addedInput schema / properties / viewportWidth

Added value: +{
+  "description": "Exact viewport width in pixels. Overrides viewport.",
+  "maximum": 3840,
+  "minimum": 320,
+  "type": "integer"
+}

addedInput schema / properties / waitFor

Added value: +{
+  "description": "Extra milliseconds to let the page settle before capture.",
+  "maximum": 30000,
+  "minimum": 0,
+  "type": "integer"
+}

First observedAug 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, so safety is largely covered. The description adds that rendering happens in a real browser and that the result is a hosted PNG at a public URL, but it omits the persistent caching/storage side effect (readOnlyHint=false) that the schema alone explains.

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 before the usage cue. 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?

With no output schema, the description correctly states the return value (a PNG at a public URL), and the 8 parameters are fully covered by the schema. Only the caching/persistence behavior of the capture is left implicit.

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%, so every parameter (maxAge caching, timeout, waitFor, fullPage, viewport overrides) is already fully documented. The description adds no parameter-level meaning beyond that, which is the expected baseline.

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?

States a specific verb and resource ('Render a page in a real browser and capture a PNG') plus the return artifact ('its public URL'). This clearly separates it from sibling text-oriented tools like scrape, extract, and crawl.

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

Usage Guidelines4/5

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

Gives an explicit selection condition: 'Use when the question is what the page looks like rather than what it says.' That implicitly routes the agent away from scrape/extract, though it never names the alternative tool.

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

All Hydrafetch tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?