URLpipe

Take a screenshot

capture_screenshot

Idempotent

Exposes POST /screenshot. Captures the whole rendered page as a PNG — JavaScript executed, web fonts and images included, exactly as a browser would draw it. 1 credit, whichever options you use.

Use it to see a page rather than read it: layout, visual regressions, link previews, or checking what an anti-bot page actually showed us. screenshot_options size it (viewport, scale, one element, the fold only), encode it (png, jpeg or webp) and restyle it (dark mode, hidden elements, your own CSS); page_options wait for the page and take ads and cookie banners out of it.

Input Schema

Name	Required	Description
`url`	Yes	The page to fetch. Must be a public http(s) URL.
`sync`	No	Wait for the result and return it (default false). When false the call returns a token immediately and you collect the result with get_result.
`labels`	No	Your own keys to find this request by later, e.g. {"client": "acme"}: they come back with the result, in the webhook and in list_requests, which can filter by them. Up to 16 keys of up to 40 letters, digits, _ - or .; string values up to 256 characters.
`max_age`	No	How fresh a stored result must be to be reused, e.g. "2 hours" or "3 days". Default 7 days, maximum 30. A reused result is free. Pass "0" to force a fresh fetch.
`report_to`	No	Async only: a webhook URL to deliver the result to. Defaults to the project's configured endpoint, if it has one.
`project_id`	Yes	Which project this request belongs to. From list_projects.
`residential`	No	Fetch the page from a residential (home ISP) exit instead of a datacentre one. Costs a surcharge per page visit — see get_usage. Use it for sites that block datacentre traffic.
`auth_profile`	No	Load the page signed in, as this auth profile's visitor: its id, ap_…. A profile is a browser's signed-in state uploaded once over the HTTP API (POST /auth_profiles); only URLs on its domains are accepted. Costs nothing extra. https://urlpipe.dev/docs/auth-profiles
`page_options`	No	What to do to the page before anything is read off it. Applies to the result itself: removed ads and banners are gone from html, markdown and summaries too, and what scrolling loaded is in all of them.
`idempotency_key`	No	Makes the call safe to retry: sending it again with the same key within 24 hours returns the first call's token and result instead of starting (and charging for) new work, even with max_age "0". Up to 255 printable ASCII characters; a UUID is ideal.
`screenshot_options`	No	How to take the screenshot. Every key is optional; leave it out for a full-page PNG.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / auth_profile

Added value: +{
+  "description": "Load the page signed in, as this auth profile's visitor: its id, ap_…. A profile is a browser's signed-in state uploaded once over the HTTP API (POST /auth_profiles); only URLs on its domains are accepted. Costs nothing extra. https://urlpipe.dev/docs/auth-profiles",
+  "type": "string"
+}

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / screenshot_options / properties / styles / description

Previous value: -"CSS to inject into the page before capturing."New value: +"CSS to inject into the page before capturing, up to 20000 characters."

Changed2 schema fields changedOct 12, 2026

changedInput schema / properties / page_options / description

Previous value: -"What to do to the page before anything is read off it. Applies to the result itself: removed ads and banners are gone from html, markdown and summaries too."New value: +"What to do to the page before anything is read off it. Applies to the result itself: removed ads and banners are gone from html, markdown and summaries too, and what scrolling loaded is in all of them."

addedInput schema / properties / page_options / properties / scroll_to_bottom

Added value: +{
+  "description": "Scroll down the page before reading it, for as long as scrolling loads more (up to 25s). For listings and feeds that load their content as they are scrolled.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / page_options / properties / block_popups

Added value: +{
+  "description": "Remove newsletter, app-install and promotional popups laid over the page.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "anyOf": [
+    {
+      "properties": {
+        "mime_type": {
+          "description": "The image's type. The image itself is the image content block.",
+          "type": "string"
+        },
+        "result_url": {
+          "description": "A link to the image that needs no key.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "mime_type"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "labels": {
+          "type": "object"
+        },
+        "status": {
+          "const": "accepted",
+          "type": "string"
+        },
+        "token": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "token",
+        "status"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

First observedSep 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context the annotations cannot carry: '1 credit, whichever options you use' and the fact that JS executes and external assets load, which affects latency and fidelity. It omits the request-record side effect (results retrievable via get_request/list_requests) and the async token flow, though the schema covers the latter.

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

Conciseness4/5

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

Front-loaded with the core action, then a compact two-sentence second paragraph that packs cost, fidelity and option groups without redundancy. The opening 'Exposes POST /screenshot' is arguably filler for an agent but is a single short clause, and the parenthetical lists stay tight.

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?

An output schema exists, so return-value explanation is rightly omitted. The description covers fidelity, cost, the see-vs-read decision and both option groups, which is enough for an 11-parameter tool with nested objects. Minor gap: nothing tells the agent that results are recorded and retrievable later, which matters for the async default.

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 is already documented in detail — baseline 3 applies. The description adds grouping value by summarizing the two nested objects as 'size it / encode it / restyle it' and 'wait for the page and take ads and cookie banners out of it', but contributes no syntax or semantics beyond what the schema states.

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?

States a concrete verb and artifact ('Captures the whole rendered page as a PNG') plus the fidelity guarantee ('JavaScript executed, web fonts and images included, exactly as a browser would draw it'). The line 'see a page rather than read it' implicitly separates it from the text-extraction siblings (fetch_html, fetch_markdown, scrape_url), but the nearest sibling, capture_pdf, is never named or contrasted.

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 concrete use cases (layout, visual regressions, link previews, verifying an anti-bot page) and a clear selection rule: use it when you need to see rather than read the page. It stops short of explicit exclusions — it never says when to prefer capture_pdf, or that text tasks should go to fetch_markdown/scrape_url.

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

All URLpipe 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?