Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

full_page_screenshot

Read-onlyIdempotent

Captures full-page screenshots by scrolling and stitching viewport-sized segments. Returns either a stitched image or individual segments, useful for layout verification when text reading is insufficient.

Instructions

Full-page capture by scrolling: stitched segments of ~2 viewports (≤1568px), or one image per viewport with stitch=false. Expensive: ~2.7k image tokens per segment, only max_segments returned, the rest via segment_offset. Reading the text you need is cheaper by an order of magnitude — prefer read_page, extract or find_text unless layout 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 (≈2.7k image tokens each); segment_offset for the rest
segment_offsetNoSkip the first N segments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • changedInput schema / properties / max_segments / description
      Previous value: -"Images returned, from the top (each ≈2.7k image tokens); raise or use segment_offset for the rest"New value: +"Images returned from the top (≈2.7k image tokens each); segment_offset for the rest"
  2. Changed2 schema fields changedv1.10.0
    • addedInput schema / properties / max_scrolls / description
      Added value: +"Cap on scroll steps: a taller page is captured only up to here"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
  3. First observedv1.8.0

TDQS

A4.8/5.0
Behavior5/5

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

Describes scroll behavior, segment stitching, token costs, and limits (max_scrolls, max_segments, offset). Consistent with readOnlyHint and idempotentHint; no contradiction, and the cost information adds transparency.

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 well-structured, front-loading the core purpose, then cost, then usage guidance. It is concise and contains no filler or redundancy, with all sentences contributing to clarity.

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?

The description covers the capture process, cost, when to use, and limits. It does not specify the exact return format (e.g., image URLs), but given the absence of an output schema, the provided information is reasonably complete for an agent to invoke it correctly.

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 descriptions are already thorough (100% coverage) and meaningfully explain each parameter. The description adds context about cost per segment, which enhances the understanding of max_segments, though not all parameters are further elaborated in the description itself.

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 function: full-page capture by scrolling, with stitching or separate viewport images. It distinguishes from other screenshot tools by mentioning the stitching behavior and segment limits.

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 when to prefer text-based tools (read_page, extract, find_text) over this screenshot tool, and provides cost trade-offs. This gives clear guidance on when to use it versus alternatives.

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

Deploy Server

Other Tools