Skip to main content
Glama
@pokutuna/mcp-chrome-tabs

@pokutuna/mcp-chrome-tabs

by pokutuna

List Tabs

list_tabs

Retrieves all open browser tabs with their titles and tab references, optionally including URLs. Use it to find the tab you need before reading or interacting with its content.

Instructions

List all open tabs in the user's browser with their titles and tab references.

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
includeUrlNoInclude URLs in the output. Enable only when you need to reference specific URLs. (default: false, hostnames always included)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.7.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the return shape (titles and tab references) but says nothing about ordering, scope limits, permission requirements, or whether it covers all windows — meaningful gaps for a browser-inspection tool.

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?

A single front-loaded sentence with zero filler; the resource and returned fields come first and nothing is repeated.

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-parameter read tool with no output schema, the description covers what the tool does and what it returns. Only minor behavioral details (ordering, window scope) are absent.

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 includeUrl parameter is fully documented in the schema, including the default and the note that hostnames are always included. The description adds no parameter meaning beyond that, so the 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 ('List') and resource ('all open tabs in the user's browser') plus the returned fields (titles and tab references). It is clearly distinguishable from read_tab_content and open_in_new_tab, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery step before read_tab_content, but the description states no when-to-use condition, no prerequisites, and no explicit alternative routing.

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

Deploy Server

Other Tools