Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

screenshot

Read-onlyIdempotent

Capture the visible viewport as a PNG, with options for preset sizes, background tab handling, and downscaling to 1568px.

Instructions

Screenshot of the visible viewport only (PNG), at the current scroll position, or one per viewport preset with presets. Read-only. Activates the tab in the background without stealing window focus, then restores the previous tab. Downscaled to ≤1568px: for fine print, element_screenshot with scale.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
presetsNoOne capture per preset, window restored; save_to = directory, one file each
save_toNoAbsolute path: write the PNG there and return the path instead of the content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.1
    • addedInput schema / properties / presets
      Added value: +{
+  "description": "One capture per preset, window restored; save_to = directory, one file each",
+  "items": {
+    "enum": [
+      "mobile",
+      "tablet",
+      "desktop"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changedv1.11.0
    • addedInput schema / properties / save_to
      Added value: +{
+  "description": "Absolute path: write the PNG there and return the path instead of the content",
+  "type": "string"
+}
  3. Changed1 schema field changedv1.10.0
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
  4. First observedv1.8.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only, idempotent, and non-destructive annotations, the description discloses a side effect (background tab activation and restoration) and a limitation (downscaling to ≤1568px). These details are not present in the annotations and materially affect how an agent should reason about the call.

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?

Two sentences, zero filler. The core purpose is front-loaded, followed by behavioral notes and an alternative. Every sentence earns its place.

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 main behavior, presets, save_to implication, side effects, and the key downscaling limitation with a concrete alternative. It relies on the schema for tab_id and save_to details, which is acceptable given the schema coverage. Minor gap: it doesn't mention what happens when no tab_id is provided, but that is already in the schema.

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?

The schema already documents all three parameters with 100% coverage. The description adds minimal new parameter-level meaning, only echoing the preset behavior. Given the high schema coverage, a baseline 3 is appropriate.

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 captures a PNG of the visible viewport only, at the current scroll position or per preset. It explicitly contrasts with element_screenshot and full_page_screenshot, making its scope unambiguous.

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?

It specifies when to use an alternative (for fine print, use element_screenshot with scale) and implies not for full-page captures by saying 'visible viewport only'. However, it does not enumerate all sibling alternatives or explicitly state when to prefer full_page_screenshot.

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