Skip to main content
Glama

pilot_tabs

List all open browser tabs with URLs, titles, and active status for browser automation tasks.

Instructions

List all open browser tabs with URLs, titles, and active status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'pilot_tabs' tool, which fetches and lists browser tabs.
    server.tool(
      'pilot_tabs',
      'List all open browser tabs with URLs, titles, and active status.',
      {},
      async () => {
        await bm.ensureBrowser();
        try {
          const tabs = await bm.getTabListWithTitles();
          const text = tabs.map(t =>
            `${t.active ? '→ ' : '  '}[${t.id}] ${t.title || '(untitled)'} — ${t.url}`
          ).join('\n');
          return { content: [{ type: 'text' as const, text }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
  • Registration of the tab tools, including 'pilot_tabs', within the main registration module.
    registerTabTools(effectiveServer, bm);
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It specifies returned fields (URLs, titles, active status) which helps compensate for missing output schema, but omits safety characteristics (read-only nature), pagination limits, or performance implications of querying all tabs.

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 efficient sentence with action front-loaded. Every clause serves a purpose: 'List' (operation), 'all open browser tabs' (scope), 'URLs, titles, and active status' (output specification). Zero redundancy.

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?

Appropriately complete for a zero-parameter inspection tool. The description effectively substitutes for missing output schema by enumerating return fields. Minor gap: lacks explicit confirmation of read-only safety given absence of annotations.

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?

Zero parameters present, which per guidelines warrants baseline score of 4. No parameter description needed or expected.

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?

Clear specific verb 'List' with resource 'open browser tabs'. The phrase 'with URLs, titles, and active status' precisely defines the output scope, distinguishing it from sibling manipulation tools like pilot_tab_new or pilot_tab_close.

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?

Implies inspection use case through the verb 'List', but provides no explicit when-to-use guidance or differentiation from pilot_tab_select (which requires knowing tab IDs potentially discovered via this tool). No prerequisites or conditions mentioned.

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/TacosyHorchata/Pilot'

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