Skip to main content
Glama

list_tabs

Lists open tabs in an attached CDP session, returning index, title, and URL for each so you can target the right tab.

Instructions

List the candidate tabs of an ALREADY-ATTACHED CDP session (index/title/url only). Read-only; requires nothing beyond a completed attach_browser().

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description does the work itself: it declares the operation read-only, notes it requires nothing beyond an existing attach, and limits the returned data to index/title/url (i.e., no page content). It does not say what happens when no session is attached, which is the remaining behavioral unknown.

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 short sentences with no filler; the scoping constraint and the returned fields come first, and the read-only/precondition note follows. Every clause carries information.

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-argument, read-only listing tool with no output schema, the description covers purpose, precondition, and returned fields — enough to call it correctly. The only gap is the failure mode when no CDP session is attached.

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's mention of index/title/url describes return shape rather than inputs, which is a small bonus rather than a parameter clarification.

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?

The description gives a specific verb ('List') and a precisely scoped resource ('candidate tabs of an ALREADY-ATTACHED CDP session'), and even enumerates the returned fields (index/title/url only). The emphasis on 'ALREADY-ATTACHED' and the reference to attach_browser() makes the boundary against the attach step 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?

It states a clear precondition for use — a completed attach_browser() call — which is the main gating condition an agent needs. It does not name any alternative tool or state what to do if no session is attached, so it stops short of full when/when-not guidance.

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