Skip to main content
Glama
IGELHARINE

CDPM

by IGELHARINE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Snapshot

browser_snapshot

Reads a Chrome tab as accessibility-tree text with element refs, filters, and paging, helping CDPM agents inspect pages and act on interactive elements.

Instructions

Reads the tab as accessibility-tree text. Clickable/typable elements get refs like [e12]. Long pages are split; only page 1 (top) is shown (page=2 to continue; refs stay the same across pages). find="text" shows only matching elements with their parent context; ref="e40" shows only that element's subtree. Refs change when the page changes, so re-snapshot before acting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoOnly this ref element and its subtree
tabNoTarget tab: number (1, 2…) or ID ("t7"). Use the stable ID when agents share a slot. Required for action tools when there are multiple tabs.
findNoOnly lines containing this text, with parent context (ignores case and spaces). If unsure of site language, use | for alternatives, e.g. "제목|subject"
pageNoPage number for long output (default 1)
slotYesBrowser slot 1-30. "3", "slot 3", "browser 3" → 3. If the user gives a port like 14052, subtract 14049.
agentNoYour display name, shown to other agents. Subagents must always set it. Default "claude-68d9".
multiSlotNotrue only when one agent must handle several slots together (e.g. comparing). Normally omit (one agent = one slot; use subagents for the rest)
interactiveNoOnly actionable elements (lines with refs): inputs, buttons, links. Use first to find inputs on big pages like Gmail

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the read model, ref-stability across pages, ref invalidation on page change, and the page-1-only default. It does not discuss auth, rate limits, or failure behavior, but for a read tool that is a minor gap.

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?

Four tight sentences with no filler, front-loaded with what the tool returns, then the ref/pagination mechanics, then the critical 're-snapshot' warning. Every sentence carries information an agent needs to call it correctly.

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?

For an 8-param tool with no output schema and no annotations, the description adequately covers output format, ref lifecycle, and pagination. The ancillary params (slot, agent, multiSlot) are left to the schema, which is reasonable at 100% coverage, but the description could have reiterated the multi-tab warning surfaced there.

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 description coverage is 100%, so the schema already documents all 8 params, setting a baseline of 3. The description adds real value beyond it by explaining the pagination contract (only page 1 shown, refs stay stable across pages) and the parent-context behavior of find=, which the schema does not fully convey.

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: 'Reads the tab as accessibility-tree text,' with concrete output detail (refs like [e12]). This is clearly distinct from a plain text extractor, but the description never names a sibling tool, so it stops short of explicit 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?

Gives real operational guidance: how to continue long pages (page=2), how to narrow with find= and ref=, and the key rule 're-snapshot before acting' once refs change. It never states when NOT to use this versus browser_text or browser_screenshot, so it lacks explicit 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