Skip to main content
Glama

browser_get_frames

browser_get_frames
Read-onlyIdempotent

List frames inside a Chrome tab, including iframes and blank-src app frames, then use returned frame IDs to read pages or act on elements within the right frame.

Instructions

List the frames inside a tab: iframes and blank-src app frames included. Frame 0 is the top document. Pass a returned frame_id to page reads and element actions to work inside that frame.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_get_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuine behavioral detail beyond them: the frame enumeration includes iframes and blank-src app frames, and index 0 is always the top document. It does not describe pagination, ordering beyond frame 0, or how many frames may be returned.

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?

Three short sentences, front-loaded with what is listed and immediately followed by the payoff (pass frame_id downstream). No filler, and the non-obvious edge case about blank-src app frames is worth its words.

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?

There is no output schema, so the description must carry return semantics; it does this partially by naming frame_id and defining frame 0 as the top document. It omits what else a frame entry contains (name, url, depth) which the agent needs to select the right frame.

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 tab_id, session_id and session_name are fully documented in the schema itself, including the multi-session ownership rule and session_name stickiness. The description adds no parameter-level meaning beyond implying tab_id scoping; the frame_id mention refers to an output, not an input.

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 ('List the frames inside a tab') and scopes it precisely, noting that iframes and blank-src app frames are included and that frame 0 is the top document. It does not name or explicitly contrast a sibling tool, so differentiation is inferential rather than stated.

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 clear usage context: the returned frame_id is what you pass to page reads and element actions to operate inside a frame, which establishes this as the discovery step before frame-scoped operations. It stops short of naming alternatives or stating when not to call it (e.g., top-frame-only work).

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