Skip to main content
Glama

Capture website screenshot

capture_screenshot

Capture web page screenshots using a real browser with options for viewport size, full-page capture, ad removal, and proxy country selection.

Instructions

Take a screenshot of a web page with Site-Shot and return it as an image. Renders in a real Chromium browser. Supports viewport/device sizing, full-page capture, country proxies, and automatic ad & cookie-banner removal (cleaner image, fewer vision tokens).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the web page to capture.
widthNoViewport width in pixels (default 1280).
heightNoViewport height in pixels (default 1024).
formatNoImage format. Default: png.
block_adsNoRemove ads for a cleaner screenshot. Default: true.
block_cookie_bannersNoRemove cookie-consent banners/popups. Default: true.
countryNoRender through a proxy in this country, e.g. "Germany" (auto-sets IP, language, time zone, geolocation).
languageNoOverride browser language, e.g. "de".
time_zoneNoOverride time zone, e.g. "Europe/Berlin".
geolocationNoOverride geolocation as "lat,lng".
wait_msNoMilliseconds to wait after load before capturing (for SPAs/animations).
max_heightNoCap the captured height in pixels (max 20000).
full_pageNoCapture the entire scrollable page instead of just the viewport. Default: false.
Behavior4/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 use of a real Chromium browser, ad/cookie-banner removal, and various viewport/device options. Lacks details on side effects like rate limits or network usage, but is otherwise transparent.

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?

Single, well-structured sentence that front-loads the main action and lists key features without unnecessary words.

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 13 parameters and full schema coverage, the description covers major features and return type. Could add more detail on output handling or example use cases, but is fairly complete for a complex tool.

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

Parameters4/5

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

All 13 parameters are documented in the schema (100% coverage). The description adds context beyond schema by explaining how features like country proxies and ad removal work, and mentions cleaner images and fewer vision tokens.

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 the tool takes a screenshot of a web page and returns an image. It lists supported features but does not explicitly differentiate from sibling tool 'capture_full_page', though it implies full-page capture is included.

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?

No guidance on when to use this tool versus alternatives like 'capture_full_page'. No mention of prerequisites, limitations, or when not to use it.

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/site-shot/site-shot-mcp'

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