Skip to main content
Glama

browser_tabs

List open tabs in a connected Chrome or Firefox session without per-site approval, enabling users to inspect active pages for browser automation.

Instructions

List tabs in the connected browser without per-site approval.

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
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.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one meaningful trait, that listing requires no per-site approval, which tells the agent this is a low-friction call. It does not state that the operation is read-only, what a tab entry contains, or what happens when no browser is connected.

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?

One short sentence with the resource and the key qualifier front-loaded; no filler or restatement of the tool name. Nothing is wasted, though the trailing approval clause is compressed enough to be slightly ambiguous.

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?

This is a simple, low-risk tool with one optional, fully documented parameter, so little explanation is required. However, with no output schema and no mention of what tab information comes back, an agent cannot anticipate the response shape.

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?

There is a single optional parameter and schema coverage is 100%, so the schema already explains the browser id and the chrome/firefox shorthand. The description adds no further meaning about resolution behavior or what happens when the id is omitted. Baseline 3 applies when the schema does the heavy lifting.

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 tabs in the connected browser." That is unambiguous and distinct from the sibling browser_list, which operates on browsers rather than tabs. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

The phrase "without per-site approval" implies a context where this tool is preferable to a permission-gated alternative, but the description never names that alternative or states when to reach for this versus another observation tool. Usage is implied rather than directed.

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