Skip to main content
Glama

tab_list

Lists all open browser tabs grouped by window with IDs, titles, URLs, and active/focused markers so you can find the right tab before switching or reading it.

Instructions

List every open tab in the user's own browser, grouped by window: tab id, title and URL, with the active tab of each window and the focused window marked. Use it to find a tab before tab_switch or tab_read.

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": "tab_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/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 and does well: it discloses the return structure (per-window grouping, id/title/URL, active and focused markers) and implies a non-mutating read via 'List'. It omits operational traits such as cost or behavior with many windows, so not 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both front-loaded: the first defines what the list contains, the second defines when to call it. No redundant restatement of the tool name and no filler.

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?

With no output schema, the description usefully documents the shape of the result set and its markers, which is the key missing structured information for a listing tool. It lacks detail on windows it might exclude (minimized/background) or result size, but nothing essential to invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; there is no parameter meaning to add. The description correctly spends no words on inputs and instead describes the return shape.

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 every open tab in the user's own browser') plus the grouping scope (by window) and what is returned (tab id, title, URL, active tab, focused window). An agent can distinguish it from tab_read and tab_switch without opening any schema.

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?

Explicitly routes the agent: 'Use it to find a tab before tab_switch or tab_read,' naming two concrete downstream alternatives and the condition that selects them. It does not address when not to use it (e.g., versus a text-search style sibling like tab_find), so it falls short of a full 5.

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