Skip to main content
Glama

list_tabs

Read-only

Lists all open tabs in a browser instance, including each tab’s ID, label, target ID, and URL, plus the active tab ID. Use it to identify tabs before controlling or debugging them.

Instructions

Lists the instance's tabs: {active_tab_id, tabs: [{tab_id, label, target_id, url}]}.

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

Input Schema

NameRequiredDescriptionDefault
instance_idNoDefault: 'default'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-rc.1

TDQS

A3.6/5.0
Behavior4/5

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

With only readOnlyHint=true in annotations, the description adds real value by enumerating the return payload: active_tab_id plus a tabs array of {tab_id, label, target_id, url}. It does not cover failure behavior for an unknown or unopened instance, but the read-only, non-mutating nature is clear.

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?

One tight sentence with the core purpose front-loaded and the field list stated compactly via inline notation. Nothing is redundant or padded.

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 one-optional-param read tool with no output schema, the description covers both intent and return structure, which is nearly everything an agent needs. Only error/edge-case behavior (empty tab list, unknown instance) is unaddressed.

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 100% and the single instance_id parameter already documents its 'default' fallback, so the schema does the heavy lifting. The description adds no meaning about what instance_id selects or how an invalid id behaves, so baseline 3 applies.

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?

The description gives a specific verb and resource ('Lists the instance's tabs') and even sketches the returned shape, so an agent can distinguish it from list_instances or list_downloads. It does not explicitly name a contrasting sibling, which keeps it just short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus tab-related siblings such as switch_tab or open_tab, and no stated precondition (e.g., that the instance must be open). Usage is only implied by the verb 'Lists'.

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