Skip to main content
Glama
escapeWu

chrome-agent-bridge

by escapeWu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Snapshot page

browser_snapshot

Capture visible page text and semantic interactive elements with short-lived refs. Use each ref with browser_act, then capture a fresh view after every action.

Instructions

Read visible page text plus semantic interactive elements with short-lived refs. Use a ref with browser_act, then take a fresh snapshot after every action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdYes
browserNoWhich connected Chrome to use: an instanceId or label from browser_list_instances. Required when more than one browser is connected; session-based tools infer it from their sessionId.
maxCharsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.1
    • addedInput schema / properties / browser
      Added value: +{
+  "description": "Which connected Chrome to use: an instanceId or label from browser_list_instances. Required when more than one browser is connected; session-based tools infer it from their sessionId.",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}
  2. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that refs are short-lived and must be refreshed after each action, but says nothing about output shape, tab-state requirements, or what maxChars truncation does to the returned content.

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 tightly written sentences with zero filler; the core capability is front-loaded ahead of the workflow instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations mean the description must cover more ground. It handles the ref lifecycle well but omits parameter guidance and return-format expectations, which is a meaningful gap for a 3-param read tool.

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

Parameters2/5

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

Schema coverage is only 33%, yet the description mentions none of the three parameters (tabId, browser, maxChars). It does not compensate for the undocumented tabId and maxChars, leaving parameter meaning entirely to the thin schema.

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?

States a specific verb and resource: read visible page text plus semantic interactive elements. This implicitly distinguishes it from browser_screenshot (visual capture), but it never names a sibling or explicitly contrasts scope, so it stops short of full differentiation.

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?

Provides clear workflow context: use a ref with browser_act, then take a fresh snapshot after every action. That tells the agent when this tool fits into the act-observe loop, though it names no exclusions or alternative read tools.

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