Skip to main content
Glama

screenshot_url

Capture a web page screenshot as a base64 PNG using a headless browser with JavaScript execution. Supports viewport settings and full page capture for visual regression, archiving, or preview generation.

Instructions

Capture a screenshot of a web page and return it as a base64-encoded PNG.

Renders the page in a headless Chromium browser with JavaScript execution,
waits for network idle (all resources loaded), then captures the viewport
or full page. Useful for visual regression checks, archiving page state,
generating previews, or letting an AI model analyse page layout.

Args:
    url: Full URL of the page to capture (must include https://).
    width: Viewport width in pixels (default 1280, range 320–3840).
    height: Viewport height in pixels (default 800, range 200–2160).
    full_page: If True, capture the full scrollable page height rather
               than just the visible viewport. May be slow for long pages.

Returns:
    png_b64: Base64-encoded PNG image data.
    w: Actual image width in pixels.
    h: Actual image height in pixels.
    bytes: File size of the PNG in bytes.
    ms: Time taken to render and capture in milliseconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
widthNo
heightNo
full_pageNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: headless Chromium, JavaScript execution, waits for network idle, captures viewport or full page, performance warning for long pages. Return fields are also described. No contradictions.

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?

Description is well-structured with a clear lead sentence, followed by technical details, then argument and return descriptions. Slightly lengthy but each sentence adds value. Could be slightly tighter, but still good.

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?

No output schema, but description explains all return fields (png_b64, w, h, bytes, ms). Covers key constraints and performance hint. Fully sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must and does add meaning for all 4 parameters. It documents the URL requirement (https://), ranges and defaults for width/height (320–3840, 200–2160), and the full_page effect and performance trade-off.

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?

Description uses specific verb 'Capture a screenshot' and resource 'web page', clearly stating it returns base64 PNG. It lists concrete use cases (visual regression, archiving, previews, AI analysis). No sibling tools perform similar function, so no confusion.

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?

The description implies when to use: for capturing page state, visual checks, or AI analysis. It does not explicitly state when not to use or provide alternatives, but given the uniqueness of the tool among siblings, it is clear enough.

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/ForeverTools/kiprio-mcp'

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