Skip to main content
Glama

browser_list_tabs

browser_list_tabs
Read-onlyIdempotent

List Chrome tabs without switching the active tab so you can find a tab_id for later actions. Returns your session's and unclaimed tabs; pass include_all to see every tab.

Instructions

List Chrome tabs without changing the active tab. Start here to find a tab_id. Only this conversation tabs and unclaimed tabs are returned, with other_session_tabs counting what was hidden; pass include_all to see every tab.

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

Input Schema

NameRequiredDescriptionDefault
window_idNo
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
include_allNoInclude tabs another session holds. Default false.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them by disclosing the default result set (this conversation's tabs plus unclaimed tabs), the existence of an other_session_tabs count describing what was suppressed, and the fact that the active tab is untouched. That is exactly the scoping and side-effect context an agent cannot get from the schema.

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?

Three short sentences, front-loaded with the purpose and the read-only guarantee, then the entry-point cue, then the filtering exception. No filler and nothing buried.

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?

For a 4-parameter read tool with no output schema, the description covers the essential behavior: what is returned by default, how to widen it, and that the active tab is preserved. The only gaps are window_id and the rename semantics of session_name, both of which the schema documents.

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 75%, so the schema is already carrying most parameter meaning, and the description correctly explains what include_all changes relative to the default filtered view. It adds nothing about window_id or the sticky session_name naming behavior, leaving two parameters to the schema alone; the 3 baseline is the right landing spot.

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 Chrome tabs") and immediately delimits it with a non-obvious constraint ("without changing the active tab"), which separates it from browser_switch_tab. The follow-up sentence positions it as the entry point for obtaining a tab_id, so its role in the workflow is unambiguous.

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 clear when-to-use guidance: read this first to find a tab_id, and pass include_all when the hidden tabs matter. It does not explicitly name an alternative tool or state when not to use it, so it stops short of full exclusion-based routing.

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