Skip to main content
Glama

browser_frames

Lists frame IDs and URLs within a browser tab so page tools can target the correct frame.

Instructions

List frame ids and URLs for use in page tools.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' weakly implies a read-only operation, but nothing states whether it requires an attached/active tab, what happens with cross-origin frames, or how the result is shaped (flat vs nested) — all material for a frame-enumeration tool.

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?

A single short sentence, front-loaded with the verb and the exact payload returned, with zero filler. It is arguably clipped to a fault, but nothing is redundant.

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

Completeness3/5

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

For a two-parameter, no-output-schema, no-annotation tool the description covers what it returns at a high level ('frame ids and URLs'). It leaves gaps an agent would want: whether the main frame is included, whether frames are top-level only, and any prerequisite state for the tab.

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%, documenting tabId as coming from browser_tabs and browser as an id from browser_list, so the schema does the parameter work. The description adds no additional meaning about how tabId or browser scoping affects the returned frame set; baseline 3 applies.

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 frame ids and URLs' for a given tab. That is clearly distinguishable from browser_tabs (tabs, not frames) and from the page-interaction siblings that consume frame ids, though the description never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'For use in page tools' implies the call is a discovery/prerequisite step before frame-scoped page operations, which is useful implied guidance. It does not state when not to call it (e.g., single-frame pages) or which tools accept the returned ids.

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