Skip to main content
Glama
frsorrentino

Chrome Bridge

by frsorrentino
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_interactives

Read-onlyIdempotent

List actionable page elements with ready-to-use CSS selectors, labels, positions, and refs for click, type, or hover. Use it to discover selectors without dumping HTML.

Instructions

List actionable elements (buttons, links, inputs, [role], [onclick]) with ready-to-use CSS selector, label, position, flags. Prefer this over dumping HTML to discover selectors. Document order, cut at limit (count equal to limit: there may be more), each with a ref (n1, n2…) for click, type_text and hover.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax elements returned; raise it on a dense page
scopeNoLimit search (CSS selector)
sinceNocursor from the previous list: only added (+), changed (~) and removed elements; same scope, frame and tab
formatNolines is compact; json adds full attributes per elementlines
tab_idNoTarget tab; omitted = last tab navigated in this session, else the active one
frame_idNoTarget iframe id from get_frames; omitted = main frame
visible_onlyNofalse also lists elements hidden or scrolled out of view

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • addedInput schema / properties / since
      Added value: +{
+  "description": "cursor from the previous list: only added (+), changed (~) and removed elements; same scope, frame and tab",
+  "type": "string"
+}
  2. Changed5 schema fields changedv1.10.0
    • addedInput schema / properties / format / description
      Added value: +"lines is compact; json adds full attributes per element"
    • addedInput schema / properties / frame_id / description
      Added value: +"Target iframe id from get_frames; omitted = main frame"
    • addedInput schema / properties / limit / description
      Added value: +"Max elements returned; raise it on a dense page"
    • addedInput schema / properties / tab_id / description
      Added value: +"Target tab; omitted = last tab navigated in this session, else the active one"
    • addedInput schema / properties / visible_only / description
      Added value: +"false also lists elements hidden or scrolled out of view"
  3. First observedv1.8.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: results are in document order, and 'count equal to limit' signals possible truncation so the agent can raise the limit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences, front-loaded with what the tool returns before the routing advice and ref usage. Every clause carries information, though the parenthetical on limit is slightly terse.

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 a read-only listing tool with full schema coverage and no output schema, the description supplies the missing return-shape context (selector, label, position, flags, refs) and the truncation caveat. It is complete enough to call correctly, missing only explicit return formatting per 'format' value.

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?

Schema description coverage is 100%, so limit, scope, since, format, tab_id, frame_id and visible_only are all already documented with defaults. The description only reinforces the limit truncation semantics and does not add format or selector syntax beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource (list actionable elements) and enumerates what counts as actionable (buttons, links, inputs, [role], [onclick]). It also routes the agent away from the sibling behavior of dumping HTML to find selectors, making it distinguishable without opening schemas.

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?

Explicitly says 'Prefer this over dumping HTML to discover selectors' and explains the ref (n1, n2…) feeds click, type_text and hover, giving clear context for use. It stops short of naming exclusions like when query_dom or read_form would be the better choice.

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