Skip to main content
Glama

readfetch

readfetch_screenshot

Read-only

Paid routes require a funded Base USDC wallet. Use readfetch-client / @readfetch/client or the MCP signing proxy (@readfetch/mcp-x402-proxy). Direct calls without a signing client will stop at 402. Screenshot a public URL in headless Chromium (page JavaScript runs; no ad blocker) and return PNG or JPEG in JSON — image_base64, mime, width, height, status_code, billed (not a hosted URL). Scope: viewport only (full_page: false), full scrollable page (default), or one element (selector). mode caps total render time: fast (15 s), render (30 s, default), full (60 s, always full-page regardless of full_page). Set width/height before navigation (default 1280×800, max 3840×2160). delay_ms (0–30000) waits after navigation, then captures — raise it or use mode=full for slow SPAs and lazy media. Prefer readfetch_text or readfetch_scrape for extractable text; readfetch_pdf for PDF files; readfetch_fetch for raw HTTP without rendering. Read-only on the origin (GET + render, no form POST). Bot-check or blank frames may still return pixels with billed: false and a hint; paid x402 like other routes.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to render in headless Chromium.
modeNoWhole-call budget: fast (15 s), render (30 s, default), or full (60 s; always captures the full scrollable page).render
widthNoViewport width in pixels before navigation (default 1280, max 3840).
formatNoImage encoding for `image_base64` (png default, or jpeg).png
heightNoViewport height in pixels before navigation (default 800, max 2160).
delay_msNoMilliseconds to wait after navigation before capture (0–30000); use for SPAs and lazy-loaded content.
selectorNoCSS selector — capture that element's box only. Omit for page/viewport per full_page.
full_pageNotrue (default): entire scrollable document; false: viewport only. Ignored when mode=full.

Output Schema

NameRequiredDescriptionDefault
urlNo
hintNo
mimeNo
sizeNo
widthNo
billedNo
formatNo
heightNo
statusNo
status_codeNo
image_base64No
content_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses payment mechanics (funded Base USDC wallet, 402 without a signing client), the fact that page JavaScript runs and there is no ad blocker, that the call is a GET-and-render with no form POST, and that bot-check or blank frames can still bill as false with a hint. This is exactly the kind of operational context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The block is dense but mostly earns its words; however, it opens with billing/auth mechanics rather than the tool's purpose, burying 'Screenshot a public URL' in the middle. It also restates schema defaults (1280x800, 3840x2160) and output fields that the schema and output schema already declare.

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 an 8-parameter, open-world rendering tool, the definition covers cost/auth prerequisites, capture scope semantics, timeout behavior, and failure modes (bot checks, billed:false with hint). With an output schema present, it correctly does not need to explain return structure in depth.

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 100%, so the schema already documents every parameter and the baseline is 3. The description adds real guidance on top: mode is framed as a whole-call time budget, mode=full overrides full_page, and 'raise delay_ms or use mode=full for slow SPAs and lazy media' is operational advice not present in the schema.

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 concrete verb and resource: 'Screenshot a public URL in headless Chromium ... return PNG or JPEG in JSON.' It also enumerates the return fields and explicitly names the sibling tools it is not (readfetch_text, readfetch_scrape, readfetch_pdf, readfetch_fetch), so an agent can distinguish it without opening any 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 gives explicit routing rules: 'Prefer readfetch_text or readfetch_scrape for extractable text; readfetch_pdf for PDF files; readfetch_fetch for raw HTTP without rendering.' It also states in-scope capture modes (viewport, full page, single selector) and when to raise delay_ms, so both selection and configuration decisions are covered.

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.