Skip to main content
Glama

Browser tabs

browser_tabs
Read-onlyIdempotent

Use this when the user needs browser tabs: List debuggable Chromium tabs when CDP is known ready. If uncertain, first check computer_snapshot(browser_readiness=true, include_ui=false, include_screenshot=false, include_browser=false). When not ready, use native ui_snapshot/ui_find rather than retrying the unchanged endpoint. This read-only tool never launches a browser; use target_id/title/url returned for subsequent browser 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": {
      "device": "<device>"
    },
    "name": "browser_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoChoose a page whose title contains this text.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
endpointNoLoopback Chrome DevTools endpoint. Defaults to REMCP_CDP_URL or http://127.0.0.1:9222.
target_idNoPage target id returned by browser_tabs.
timeout_msNoTimeout in milliseconds.
url_containsNoChoose a page whose URL contains this text.

Output Schema

NameRequiredDescriptionDefault
dataNo
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered structurally. The description adds real context beyond that: it never launches a browser, it depends on CDP readiness, and its output feeds subsequent browser tools. It stops short of describing failure behavior or pagination, keeping it below a 5.

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?

Front-loaded with the use case, then the precondition, the fallback, and the read-only guarantee. Dense but every sentence carries information; the parenthetical parameter call is slightly heavy but purposeful.

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?

An output schema exists, so return values need not be explained, and the description covers the precondition, the fallback path, and the read-only nature. For a 6-parameter list tool this is nearly complete; only error/timeout behavior is left implicit.

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 the schema already documents device, endpoint, target_id, timeout_ms and filters, making 3 the baseline. The description only adds that target_id/title/url come back from this tool and are reused downstream; it says nothing extra about endpoint or timeout semantics.

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 debuggable Chromium tabs") plus a precondition (CDP known ready). It also distinguishes itself from ui_snapshot/ui_find and from browser launching, so an agent can tell it apart from siblings like browser_snapshot without opening schemas.

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

Usage Guidelines5/5

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

Explicitly says when to use it, how to verify the precondition (computer_snapshot with browser_readiness=true), and what to do when it is not ready (use ui_snapshot/ui_find rather than retrying). Names the alternatives and the conditions selecting them.

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.

Resources