Skip to main content
Glama

take_screenshot

Capture screenshots of URLs, HTML, or Markdown content with device emulation, ad blocking, and customizable styling options for visual content creation.

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
NameRequiredDescriptionDefault
urlNoURL to capture (required if no html/markdown)
htmlNoRaw HTML to render (required if no url/markdown)
markdownNoRender Markdown content as a screenshot
widthNoViewport width in pixels (default: 1280)
heightNoViewport height in pixels (default: 720)
viewportDeviceNoDevice preset for viewport emulation (e.g. "iphone_14_pro", "macbook_pro_14"). Use list_devices to see all presets.
viewportMobileNoEnable mobile meta viewport emulation
viewportHasTouchNoEnable touch event emulation
viewportLandscapeNoLandscape orientation
deviceScaleFactorNoDevice pixel ratio, use 2 for retina (default: 1)
formatNoImage format (default: png)
qualityNoJPEG/WebP quality 1-100 (default: 80)
omitBackgroundNoTransparent background (PNG/WebP only)
fullPageNoCapture the full scrollable page (default: false)
fullPageScrollNoAuto-scroll page before capture to trigger lazy-loaded images
fullPageScrollDelayNoDelay between scroll steps in ms (default: 400)
fullPageScrollByNoPixels to scroll per step (default: viewport height)
fullPageMaxHeightNoMaximum pixel height cap for full-page captures
selectorNoCSS selector to capture a specific element
clipNoCrop region { x, y, width, height } in pixels
delayNoMilliseconds to wait before capture (default: 0)
waitUntilNoWhen to consider navigation finished (default: networkidle2)
waitForSelectorNoWait for this CSS selector to appear before capturing
navigationTimeoutNoNavigation timeout in ms (default: 25000)
darkModeNoEmulate dark color scheme (default: false)
reducedMotionNoEmulate prefers-reduced-motion to disable animations
mediaTypeNoEmulate CSS media type
timeZoneNoOverride browser timezone (e.g. "America/New_York")
geolocationNoEmulate geolocation { latitude, longitude, accuracy? }
userAgentNoOverride the browser User-Agent string
cookiesNoCookies to set — array of "name=value" strings or { name, value, domain? } objects
headersNoExtra HTTP headers to send with the request
authorizationNoAuthorization header value (e.g. "Bearer <token>")
bypassCSPNoBypass Content-Security-Policy on the page
hideSelectorsNoArray of CSS selectors to hide before capture
clickNoCSS selector to click before capturing the screenshot
injectCssNoCustom CSS to inject before capturing (max 50KB)
injectJsNoCustom JavaScript to execute before capturing (max 50KB)
blockBannersNoHide cookie consent banners (default: false)
blockAdsNoBlock advertisements on the page
blockChatsNoBlock live chat widgets on the page
blockTrackersNoBlock tracking scripts on the page
blockRequestsNoURL patterns to block (array of strings)
blockResourcesNoResource types to block (e.g. ["image", "font"])
extractMetadataNoExtract page metadata (title, description, OG tags) alongside the screenshot
styleNoScreenshot 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.
session_idNoPersistent 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.
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions capabilities like device emulation, ad blocking, and styling, which are useful context. However, it lacks details on performance (e.g., execution time, rate limits), error handling, or side effects (e.g., whether it modifies the input). It adequately describes what the tool does but misses operational nuances.

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?

The description is front-loaded with the core purpose and key features in a single, efficient sentence. It avoids redundancy and is appropriately sized for a complex tool. However, it could be slightly more structured by grouping related features (e.g., separating capture options from styling) for better readability.

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 high complexity (47 parameters, nested objects) and lack of annotations or output schema, the description does a good job of summarizing capabilities. It covers input types (URL, HTML, Markdown), key features, and output format. However, it could better address behavioral aspects like performance or error cases to be fully complete for such a multifaceted 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?

Schema description coverage is 100%, so the schema already documents all 47 parameters thoroughly. The description adds minimal value by listing features like device emulation and styling, which map to some parameters, but does not provide additional syntax or format details beyond what the schema specifies. This meets the baseline for high schema coverage.

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's purpose with a specific verb ('Capture') and resource ('screenshot of a URL, HTML, or Markdown content'), distinguishing it from siblings like create_og_image (which creates images from templates) or generate_pdf (which outputs PDFs). It explicitly mentions the output format ('Returns an image'), further differentiating it.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing a URL or content, or compare it to siblings like inspect_page (which might analyze rather than capture) or record_video (which captures video). Usage is implied but not explicitly stated.

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/Custodia-Admin/pagebolt-mcp'

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