Skip to main content
Glama

browser_frames

Read-onlyIdempotent

List the page's frames (the main frame and every ): index, name, url, whether it is the main frame, and a CSS selector matching its element only (inside its parent document: for a nested frame join the ancestors' selectors with ' >>> ', outermost first). Use the selector as frame on click / fill / type / hover / get / save_page. aria-refs from browser.snapshot work in iframes without it.

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": {
      "page_id": "<page_id>"
    },
    "name": "browser_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral detail: the selector is scoped to the parent document and nested frames are joined with ' >>> ', outermost first. It does not disclose ordering guarantees, cross-origin iframe behavior, or what happens when no frames exist.

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?

Three sentences, front-loaded with the return shape, then usage, then an escape hatch. The nested-selector parenthetical is dense but load-bearing. Minor cost: the `frame` parameter list and the '>>>' rule could be split for faster scanning.

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?

With no output schema, the description carries the return-shape burden and does so well by enumerating the five fields. Gaps remain around the required page_id and around frame ordering or cross-origin handling, but for a read-only listing tool this is largely sufficient to call correctly.

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 50%: `in_workspace` is documented in the schema while `page_id` is undocumented in both schema and description. The description mentions no parameters at all, so the required `page_id` is only inferable from 'the page's frames', and nothing clarifies what a page_id is in this browser session. The description fails to compensate for the coverage gap.

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 the page's frames') and enumerates exactly what each entry contains: index, name, url, main-frame flag, and a parent-document CSS selector. The mention of browser.snapshot aria-refs lets an agent distinguish this tool from the snapshot path without opening either schema.

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 concrete downstream usage ('Use the selector as `frame` on click / fill / type / hover / get / save_page') and hints at when it is unnecessary ('aria-refs from browser.snapshot work in iframes without it'). What's missing is an explicit statement of when the selector form is required over aria-refs (e.g., parent-document or cross-frame targeting).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.