Skip to main content
Glama

full_page_screenshot

Read-onlyIdempotent

Capture full-page screenshots by scrolling and stitching viewport segments. Returns top segments first; retrieve the rest with segment_offset.

Instructions

Full-page capture by scrolling: stitched segments of ~2 viewports (≤1568px, top→bottom), or one image per viewport with stitch=false. Read-only, but expensive: each segment costs ~2.7k image tokens, so only the first max_segments are returned and the rest need segment_offset. On a long page, reading the text you actually need is cheaper by an order of magnitude — prefer read_page, extract or find_text unless the layout itself is the question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNoms between captures (min 500, Chrome quota)
stitchNofalse = one image per viewport
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
max_scrollsNoCap on scroll steps: a taller page is captured only up to here
max_segmentsNoImages returned, from the top (each ≈2.7k image tokens); raise or use segment_offset for the rest
segment_offsetNoSkip the first N segments
Behavior5/5

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

Describes expensive token cost, segment limit, scrolling process, and Chrome quota for delay, adding context beyond read-only and idempotent annotations.

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?

Front-loaded with main action, then details; every sentence adds value without unnecessary words.

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?

Comprehensive for a complex tool: explains return behavior, cost, pagination, and when to avoid use, despite no output schema.

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?

Schema covers all parameters with descriptions, but description adds meaningful context like Chrome quota for delay and cost implications for max_segments.

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?

Clearly defines as full-page capture via scrolling with stitching, distinguishing from single-viewport screenshot and cheaper text-reading tools like read_page.

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

Usage Guidelines5/5

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

Explicitly advises preferring read_page, extract, or find_text unless layout is needed, and explains cost and segment retrieval behavior.

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/frsorrentino/chrome-bridge'

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