Skip to main content
Glama

pilot_tab_select

Switch to a specific browser tab by ID to manage multiple web pages during automation tasks.

Instructions

Switch to a specific browser tab by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTab ID to switch to

Implementation Reference

  • The handler implementation for the 'pilot_tab_select' tool, which takes a tab ID and switches the browser focus to that tab using the BrowserManager.
    server.tool(
      'pilot_tab_select',
      'Switch to a specific browser tab by ID.',
      { id: z.number().describe('Tab ID to switch to') },
      async ({ id }) => {
        await bm.ensureBrowser();
        try {
          bm.switchTab(id);
          return { content: [{ type: 'text' as const, text: `Switched to tab ${id}` }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It omits critical behavioral details: that this changes the active browsing context for subsequent operations, what happens if the ID is invalid, or whether this waits for tab load completion.

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, zero fluff. Appropriate length for the tool's simplicity. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Minimal but adequate for a single-parameter action tool. However, given no output schema or annotations, and considering this is a stateful context-switching operation, it lacks explanation of side effects on subsequent operations. Meets viability but leaves operational gaps.

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% (the 'id' parameter is well-described in schema as 'Tab ID to switch to'). The description mentions 'by ID', confirming the parameter's purpose, but adds no additional semantic information (format constraints, how to obtain IDs) beyond the schema.

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?

Clear verb (switch to), resource (browser tab), and mechanism (by ID). However, it does not explicitly distinguish from siblings like pilot_tabs (listing) or pilot_tab_new (creating), which would help clarify when to use this specific tool.

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?

Provides no guidance on when to use versus alternatives (e.g., pilot_navigate for new URLs), nor prerequisites like obtaining the tab ID from pilot_tabs first. No mention of error conditions or when not to use.

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