PageShot

batch_screenshot

Capture screenshots of multiple URLs in a single request. Returns base64-encoded images. Maximum 5 URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`urls`	Yes	Array of URLs to screenshot (max 5)
`width`	No	Viewport width (default: 1280)
`format`	No	Image format (default: png)
`height`	No	Viewport height (default: 720)
`locale`	No	BCP 47 locale tag for the browser context (e.g., "en-US")
`latitude`	No	Geolocation latitude (-90 to 90)
`timezone`	No	IANA timezone for the browser context (e.g., "America/New_York")
`dark_mode`	No	Enable dark mode emulation
`full_page`	No	Capture full page scroll height
`longitude`	No	Geolocation longitude (-180 to 180)
`wait_until`	No	Page load strategy (default: domcontentloaded). Use "networkidle" for SPAs.
`disable_javascript`	No	Disable JavaScript execution on the page
`ignore_https_errors`	No	Ignore HTTPS/TLS certificate errors

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedMar 13, 2026

addedInput schema / properties / ignore_https_errors

Added value: +{
+  "description": "Ignore HTTPS/TLS certificate errors",
+  "type": "boolean"
+}

addedInput schema / properties / wait_until

Added value: +{
+  "description": "Page load strategy (default: domcontentloaded). Use \"networkidle\" for SPAs.",
+  "enum": [
+    "commit",
+    "domcontentloaded",
+    "load",
+    "networkidle"
+  ],
+  "type": "string"
+}

Changed3 schema fields changedMar 11, 2026

addedInput schema / properties / disable_javascript

Added value: +{
+  "description": "Disable JavaScript execution on the page",
+  "type": "boolean"
+}

addedInput schema / properties / latitude

Added value: +{
+  "description": "Geolocation latitude (-90 to 90)",
+  "maximum": 90,
+  "minimum": -90,
+  "type": "number"
+}

addedInput schema / properties / longitude

Added value: +{
+  "description": "Geolocation longitude (-180 to 180)",
+  "maximum": 180,
+  "minimum": -180,
+  "type": "number"
+}

Changed2 schema fields changedMar 10, 2026

addedInput schema / properties / locale

Added value: +{
+  "description": "BCP 47 locale tag for the browser context (e.g., \"en-US\")",
+  "type": "string"
+}

addedInput schema / properties / timezone

Added value: +{
+  "description": "IANA timezone for the browser context (e.g., \"America/New_York\")",
+  "type": "string"
+}

AddedMar 6, 2026

TDQS

A3.6/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. It discloses the output format (base64-encoded images) and the 5-URL limit, but does not mention error handling, partial failures, or side effects (e.g., network activity). This is minimal but better than no disclosure.

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?

The description is two concise sentences with no filler. The action, output format, and key constraint are front-loaded, making it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 13 parameters and no output schema, the description should specify the return structure (e.g., array of base64 strings mapped to URLs) and clarify behavior if some URLs fail. It only says 'returns base64-encoded images', which is ambiguous for a batch operation. The rich schema covers parameters, but return/error handling is incomplete.

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 coverage is 100%, with every parameter having a description including defaults and constraints. The tool description adds no extra parameter details beyond what the schema already provides, so the baseline 3 applies.

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 clearly states the tool captures screenshots of multiple URLs in a single request, distinguishing it from single-screenshot or PDF-generation siblings. The verb 'capture screenshots' plus the resource 'multiple URLs' makes the purpose explicit.

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

Usage Guidelines3/5

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

The description implies this is for batch scenarios ('multiple URLs', 'single request', 'Maximum 5 URLs') but does not explicitly compare to take_screenshot or other alternatives. No exclusions or when-not-to-use guidance is provided.

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

All PageShot tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation4/5

take_screenshot and batch_screenshot both capture screenshots, but batch_screenshot handles multiple URLs while take_screenshot handles a single page, making them distinct enough. render_html and generate_pdf are clearly separate (image vs. PDF, HTML input vs. URL/HTML). Minor confusion possible between the two screenshot tools.

Naming Consistency4/5

Three tools follow the verb_noun pattern (take_screenshot, generate_pdf, render_html), but batch_screenshot breaks the pattern by leading with an adjective/noun rather than a verb. The inconsistency is minor and the names remain readable.

Tool Count5/5

Four tools is well-scoped for a page capture server. Each tool covers a distinct use case: single screenshot, batch screenshot, HTML rendering to image, and PDF generation. No redundancy or excessive bloat.

Completeness4/5

The set covers core web capture needs: single page screenshots, batch captures, HTML/CSS to image, and PDF conversion. Minor gaps include no explicit full-page screenshot option or advanced viewport control, but common workflows are supported.

Resources

Need Help?