Skip to main content
Glama

browser_tabs

Lists browser page targets on a configured port, using CDP or BiDi to let agents discover open tabs, including Firefox Remote Agent targets.

Instructions

List browser page targets on the configured port. Use protocol=bidi for Firefox Remote Agent.

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_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
protocolNocdp
host_headerNoBiDi Host header; use localhost:9222 through SSH forwarding

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only enumeration but never says so explicitly, and it omits whether the browser must already be launched, what happens when nothing is listening on the port, or whether it attaches or spawns a target — all material for a browser-control tool.

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?

Two short sentences with zero filler, and the core behavior is front-loaded ahead of the conditional protocol hint. Nothing could be removed without losing information.

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

Completeness2/5

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

With no annotations, no output schema, and a third of parameters undocumented, the description should cover the return shape (what a "target" contains) and the launch precondition. Neither appears, leaving an agent unable to predict results or recover from a dead port.

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 coverage is 33%: host_header is documented in the schema, while port and protocol are not. The description compensates for protocol by mapping bidi to Firefox Remote Agent, and gestures at port via "configured port," but adds no format or range detail for port and gives no failure semantics for either.

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?

The description opens with a specific verb and resource — "List browser page targets on the configured port" — which is clearly distinct from mutation-oriented siblings such as browser_launch, browser_click, and browser_type. It stops short of naming or contrasting an alternative, so it falls just under the top mark.

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

Usage Guidelines2/5

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

The only conditional guidance is a parameter-value hint, "Use protocol=bidi for Firefox Remote Agent," which tells the agent how to configure one argument but not when to pick this tool over browser_launch or browser_scan. No prerequisites (e.g., a browser must already be running on the port) or exclusions are stated.

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