Skip to main content
Glama

browser_get_interactives

browser_get_interactives
Read-onlyIdempotent

Lists interactive page elements and their opaque element_ids so an agent can inspect a page or iframe and target the right control before performing any element action.

Instructions

List interactive page elements and their opaque element_ids. Call this before any element action. Pass frame_id to inspect an iframe; the top document is frame 0, and an element_id only works in the frame that returned it. A heavy page can hold hundreds of elements, so the list is capped at 150 and reports total plus truncated; narrow it with limit, visible_only, tag, role or name_contains instead of asking for everything.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_get_interactives"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoKeep one tag, for example button or input.
roleNoKeep one role, for example tab or combobox.
limitNoMaximum elements returned. Defaults to 150.
tab_idNoChrome tab ID. Defaults to the active tab when omitted.
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.
visible_onlyNoDrop elements that are not visible.
name_containsNoCase-insensitive substring of the element name or text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: a hard cap of 150 elements, the fact that the response reports total and truncated flags, and the frame-scoping gotcha where element_ids are only valid inside their originating frame. With no output schema, the truncation/total disclosure is the only place an agent learns the result shape.

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 sentences, front-loaded with purpose then the call-ordering rule, then frame semantics, then result-size handling. Each sentence carries a distinct decision the agent must make; nothing is padded.

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

Completeness5/5

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

For a 9-parameter read tool with no output schema, the description covers the two things an agent cannot infer from structured fields: the frame element_id scoping constraint and the truncation/total reporting. Tab and session parameters are documented in the schema, so no gap remains that would cause a mis-invocation.

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 coverage is 100%, so the baseline is 3; the description goes beyond it by explaining that frame 0 is the top document and by naming the narrowing knobs (limit, visible_only, tag, role, name_contains) as the preferred way to handle large pages. That is real guidance about how the filters interact with the result cap, not a restatement of the schema.

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 interactive page elements") plus the key return artifact ("opaque element_ids"), which immediately separates it from the page-content and screenshot siblings. The follow-on sentence that an element_id only works in the frame that returned it further anchors what this tool produces versus what the action tools consume.

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?

"Call this before any element action" gives an explicit sequencing rule, and the frame_id note explains when to use it against the frames tool. It never states a when-not or names a competing alternative for the listing itself (e.g. observe vs get_page_content), so it stops short of full routing guidance.

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