Pagebolt

take_screenshot

Capture a screenshot from a URL, HTML, or Markdown to generate PNG, JPEG, or WebP images. Apply device emulation, styling, and content blocking for clean visual output.

Instructions

Capture a screenshot of a URL, HTML, or Markdown content. Supports device emulation, ad/chat/tracker blocking, metadata extraction, geolocation, timezone, styling (macOS/Windows frames, gradient/glass backgrounds, shadows), and more. Returns an image (PNG, JPEG, or WebP).

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	URL to capture (required if no html/markdown)
`clip`	No	Crop region { x, y, width, height } in pixels
`html`	No	Raw HTML to render (required if no url/markdown)
`click`	No	CSS selector to click before capturing the screenshot
`delay`	No	Milliseconds to wait before capture (default: 0)
`style`	No	Screenshot styling options — add a macOS/Windows frame, gradient/glass background, shadow, and rounded corners. Use the "theme" shortcut for one-click presets, or customize individual properties.
`width`	No	Viewport width in pixels (default: 1280)
`format`	No	Image format (default: png)
`height`	No	Viewport height in pixels (default: 720)
`cookies`	No	Cookies to set — array of "name=value" strings or { name, value, domain? } objects
`headers`	No	Extra HTTP headers to send with the request
`quality`	No	JPEG/WebP quality 1-100 (default: 80)
`blockAds`	No	Block advertisements on the page
`darkMode`	No	Emulate dark color scheme (default: false)
`fullPage`	No	Capture the full scrollable page (default: false)
`injectJs`	No	Custom JavaScript to execute before capturing (max 50KB)
`markdown`	No	Render Markdown content as a screenshot
`selector`	No	CSS selector to capture a specific element
`timeZone`	No	Override browser timezone (e.g. "America/New_York")
`bypassCSP`	No	Bypass Content-Security-Policy on the page
`injectCss`	No	Custom CSS to inject before capturing (max 50KB)
`mediaType`	No	Emulate CSS media type
`userAgent`	No	Override the browser User-Agent string
`waitUntil`	No	When to consider navigation finished (default: networkidle2)
`blockChats`	No	Block live chat widgets on the page
`session_id`	No	Persistent session ID (Starter+ only). Reuse a live browser page created with create_session — browser state (cookies, localStorage, auth) carries over from previous requests in this session.
`geolocation`	No	Emulate geolocation { latitude, longitude, accuracy? }
`blockBanners`	No	Hide cookie consent banners (default: false)
`authorization`	No	Authorization header value (e.g. "Bearer <token>")
`blockRequests`	No	URL patterns to block (array of strings)
`blockTrackers`	No	Block tracking scripts on the page
`hideSelectors`	No	Array of CSS selectors to hide before capture
`reducedMotion`	No	Emulate prefers-reduced-motion to disable animations
`blockResources`	No	Resource types to block (e.g. ["image", "font"])
`fullPageScroll`	No	Auto-scroll page before capture to trigger lazy-loaded images
`omitBackground`	No	Transparent background (PNG/WebP only)
`viewportDevice`	No	Device preset for viewport emulation (e.g. "iphone_14_pro", "macbook_pro_14"). Use list_devices to see all presets.
`viewportMobile`	No	Enable mobile meta viewport emulation
`extractMetadata`	No	Extract page metadata (title, description, OG tags) alongside the screenshot
`waitForSelector`	No	Wait for this CSS selector to appear before capturing
`fullPageScrollBy`	No	Pixels to scroll per step (default: viewport height)
`viewportHasTouch`	No	Enable touch event emulation
`deviceScaleFactor`	No	Device pixel ratio, use 2 for retina (default: 1)
`fullPageMaxHeight`	No	Maximum pixel height cap for full-page captures
`navigationTimeout`	No	Navigation timeout in ms (default: 25000)
`viewportLandscape`	No	Landscape orientation
`fullPageScrollDelay`	No	Delay between scroll steps in ms (default: 400)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.17.0Oct 6, 2026

changedInput schema / properties / cookies / items / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "domain": {
-        "type": "string"
-      },
-      "name": {
-        "type": "string"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "value"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "domain": {
+        "type": "string"
+      },
+      "expirationDate": {
+        "type": "number"
+      },
+      "expires": {
+        "type": "number"
+      },
+      "httpOnly": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "path": {
+        "type": "string"
+      },
+      "sameSite": {
+        "enum": [
+          "Strict",
+          "Lax",
+          "None",
+          "strict",
+          "lax",
+          "no_restriction",
+          "unspecified"
+        ],
+        "type": "string"
+      },
+      "secure": {
+        "type": "boolean"
+      },
+      "url": {
+        "type": "string"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "value"
+    ],
+    "type": "object"
+  }
+]

First observedv1.8.1Mar 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the return artifact ("Returns an image (PNG, JPEG, or WebP)"), which is genuinely useful. But it omits auth needs, rate limits, and paid-tier gating, and closes with a vague "and more" rather than concrete behavior.

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?

Three sentences, front-loaded with the core action and its inputs before the feature list. The trailing "and more" is filler that could be cut, keeping it out of 5 territory.

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?

For a 47-parameter tool with no annotations and no output schema, the description covers the return format and the major capability groups, and the schema handles parameter detail exhaustively. Missing only operational context (auth, tier limits) that an agent would want before invoking.

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 the schema already documents all 47 parameters in detail. The description's feature list (device emulation, blocking, geolocation, styling) is thematic rather than parameter-level and adds little 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 specific verb+resource ("Capture a screenshot") and the three input source types (URL, HTML, Markdown). It does not differentiate itself from capture-adjacent siblings like generate_pdf, record_video, or create_og_image, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description lists capabilities but gives no when-to-use guidance, no indication of when to prefer take_screenshot over record_video or generate_pdf, and no mention of session prerequisites despite session_id being Starter+ only. An agent gets no routing help.

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

take_screenshot

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools