Skip to main content
Glama

Capture Website Screenshot (ApiFlash)

web.screenshot.capture
Read-onlyIdempotent

Take screenshots of any URL with options for full-page capture, custom viewport, ad blocking, and cookie banner removal. Waits for JS-heavy pages.

Instructions

⚡ ACTION: Take a screenshot of any URL — returns image URL. Chrome-based rendering, supports full-page capture, custom viewport, ad blocking, cookie banner removal. Waits for JS-heavy SPAs to load (ApiFlash)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the website to screenshot (e.g. "https://example.com")
formatNoImage format: "png" (default), "jpeg", or "webp"
widthNoViewport width in pixels (default 1920, max 3840)
heightNoViewport height in pixels (default 1080)
full_pageNoCapture full page scroll height (default false)
delayNoWait N seconds before capture (0-10, for JS-heavy pages)
no_adsNoBlock ads before capture (default false)
no_cookie_bannersNoRemove cookie consent banners (default false)
wait_untilNo"page_loaded" (default) or "network_idle" (wait for all XHR/fetch)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable behavioral details: Chrome-based rendering, full-page capture, ad blocking, cookie banner removal, and JS-waiting. These traits go beyond annotations and help the agent understand runtime behavior.

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 a single, well-structured sentence that immediately states the action and return value. Every phrase adds value (supports full-page, viewport, ad blocking, etc.). No fluff or redundancy.

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?

Given the tool's moderate complexity (9 parameters, output schema exists), the description covers the core purpose and key features. It does not discuss error cases or performance limits, but the output schema likely provides return structure. Overall sufficient for a read-only screenshot tool.

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?

Input schema covers all 9 parameters with descriptions (100% coverage). The description redundantly mentions features corresponding to some parameters (e.g., full_page, no_ads) but does not add new semantics beyond what the schema already provides. Baseline score of 3 is appropriate.

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?

The description clearly states 'Take a screenshot of any URL — returns image URL' with specific rendering capabilities (Chrome-based, full-page, viewport). However, it does not explicitly differentiate from the sibling tool 'web.scrape.screenshot', which may offer similar functionality.

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 usage for capturing website screenshots with various options, but lacks explicit guidance on when to use this tool versus alternatives like web.scrape.screenshot or other web tools. No 'when not to use' or contextual conditions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server