Skip to main content
Glama
pokutuna

@pokutuna/mcp-chrome-tabs

by pokutuna

List Tabs

list_tabs

Retrieve all open browser tabs with titles and references. Use to manage multiple tabs, access current content, or organize browsing sessions.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeUrlNoInclude URLs in the output. Enable only when you need to reference specific URLs. (default: false, hostnames always included)

Implementation Reference

  • The handler function for the list_tabs tool in src/mcp.ts, which calls listTabs and formats the output.
    async (args) => {
      const { includeUrl } = args;
      const tabs = await listTabs(options);
      return {
        content: [
          {
            type: "text",
            text: view.formatList(tabs, includeUrl),
          },
        ],
      };
    }
  • The helper function listTabs that retrieves the browser tab list and filters excluded hosts.
    async function listTabs(opts: McpServerOptions): Promise<Tab[]> {
      const browser = getInterface(opts.browser);
      const tabs = await browser.getTabList(opts.applicationName);
      return tabs.filter((t) => !isExcludedHost(t.url, opts.excludeHosts));
    }
  • src/mcp.ts:110-125 (registration)
    The registration of the list_tabs tool in src/mcp.ts.
    server.registerTool(
      "list_tabs",
      {
        title: "List Tabs",
        description:
          "List all open tabs in the user's browser with their titles and tab references.",
        inputSchema: {
          includeUrl: z
            .boolean()
            .optional()
            .default(false)
            .describe(
              "Include URLs in the output. Enable only when you need to reference specific URLs. (default: false, hostnames always included)"
            ),
        },
      },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the basic read-only nature and output format (titles/references), but omits behavioral details like permission requirements, privacy considerations, or whether tab references are persistent IDs.

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?

Single sentence, front-loaded with the action verb, and zero wasted words. Every component earns its place by defining scope ('all open tabs'), location ('user's browser'), and output ('titles and tab references').

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 simple single-parameter tool without output schema, the description adequately explains what the tool returns. It could be improved by mentioning the URL inclusion option described in the schema, but it covers the core functionality sufficiently.

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 description coverage is 100%, establishing a baseline of 3. The description does not mention the includeUrl parameter or its default behavior (URLs excluded), leaving all parameter semantics to the schema itself.

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 uses a specific verb ('List') and resource ('open tabs'), and distinguishes from siblings by specifying it returns 'titles and tab references' (metadata) rather than content, clearly differentiating it from read_tab_content.

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?

While the description implies usage by stating it returns tab references (suggesting it's for discovery before reading), it lacks explicit guidance on when to use this versus read_tab_content or workflows like 'use this first to get tab IDs'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pokutuna/mcp-chrome-tabs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server