Skip to main content
Glama

Hydrafetch

by com.hydrafetch
OverviewDiscussionsAdmin

Screenshot

screenshot
Read-only

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
NameRequiredDescriptionDefault
urlYesThe URL to capture.
maxAgeNoReuse 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.
timeoutNoOverall time budget for the capture, in milliseconds.
waitForNoExtra milliseconds to let the page settle before capture.
fullPageNoCapture the whole scrollable page rather than the viewport.
viewportNoScreen size to render at. Defaults to desktop (1920x1080). Ignored when width or height are given.
viewportWidthNoExact viewport width in pixels. Overrides viewport.
viewportHeightNoExact 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.

  1. Changed6 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark the tool read-only and non-destructive. The description adds useful behavioral context: it launches a real browser (implying JavaScript execution) and returns a publicly accessible URL. Caching and freshness behavior are left to the schema's maxAge documentation, which is acceptable given the annotation coverage.

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 front-load the action and output, then provide the usage context. Every sentence earns its place, and there is no repetition of schema or annotation content.

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 read-only rendering tool, the description covers what it produces, how it produces it, and when to use it. With no output schema, mentioning the PNG and public URL return shape is valuable, and the rich input schema covers the parameters.

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%, with detailed parameter explanations covering defaults, units, overrides, and cache semantics. The description itself adds no parameter-level meaning, but it does not need to because the schema carries that burden.

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 states a specific verb and resource: render a page in a real browser, capture a PNG, and return a public URL. It also distinguishes itself from text-oriented siblings by contrasting visual appearance ('what the page looks like') with content ('what it says').

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?

It gives a clear decision rule: use when the question is visual rather than textual. This helps an agent choose it over extract/scrape-style tools, but it does not explicitly name alternatives or state when not to use it, so it falls just short of a 5.

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

All Hydrafetch toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources