chrome-dev-mcp

Overview Schema Source Related Servers Discussions Admin

list_tabs

Read-only

List open Chrome tabs to retrieve targetIds, titles, URLs, and active/connected status. Use it to identify the tab controlled by the server before switching or acting.

Instructions

List open Chrome page tabs with their targetIds, titles and URLs. active marks a tab showing on screen — the selected tab of a window that is not minimised or fully covered, so several windows mean several — and is absent if the tab did not answer. connected marks the tab this server acts on; selecting another tab in Chrome does not change it, only switch_tab does.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`tabs`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.0.0Nov 2, 2026
- removedOutput schema / properties / tabs / items / properties / active / description
```
Removed value: -"True if this tab is the current MCP target"
```
- addedOutput schema / properties / tabs / items / properties / connected
```
Added value: +{
+  "type": "boolean"
+}
```
- changedOutput schema / properties / tabs / items / required
```
Previous value: -[
-  "targetId",
-  "title",
-  "url",
-  "active"
-]New value: +[
+  "targetId",
+  "title",
+  "url",
+  "connected"
+]
```
Addedv1.3.0Aug 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely non-obvious behavior: `active` reflects on-screen visibility with the multi-window caveat, and the field is absent if the tab did not answer — an important signal about partial results that annotations cannot convey.

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?

Three sentences, front-loaded with the core purpose, then the two ambiguous output fields. Every clause carries information; the nested em-dash aside about minimised/covered windows is slightly convoluted but resolves a real ambiguity.

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 zero-parameter read tool with an output schema and readOnlyHint, this covers what an agent needs: what is listed, what the two flag fields mean, and which tab is actionable. It leaves unstated only edge cases such as zero open tabs or whether all windows/profiles are included.

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. The description correctly does not waste space on inputs and instead spends its budget on output-field 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 open Chrome page tabs') plus the exact fields returned (targetIds, titles, URLs). It is immediately distinguishable from siblings like switch_tab or get_page_info, which act on a tab rather than enumerate them.

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 context: the `connected` field identifies the tab this server acts on and notes that only switch_tab changes it, which implicitly frames this as the discovery step before switching. It never states an explicit 'use this when' or an exclusion against get_page_info, so it stops short of a 5.

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