Skip to main content
Glama

pilot_tab_new

Open a new browser tab in Pilot's persistent Chromium instance, optionally navigating to a specific URL for automated web interactions.

Instructions

Open a new browser tab, optionally navigating to a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to navigate to in the new tab

Implementation Reference

  • The handler implementation for pilot_tab_new which uses BrowserManager to create a new tab.
    server.tool(
      'pilot_tab_new',
      'Open a new browser tab, optionally navigating to a URL.',
      { url: z.string().optional().describe('URL to navigate to in the new tab') },
      async ({ url }) => {
        await bm.ensureBrowser();
        try {
          const id = await bm.newTab(url);
          return { content: [{ type: 'text' as const, text: `Opened tab ${id}${url ? ` → ${url}` : ''}` }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior3/5

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

With no annotations provided, the description carries full disclosure burden. It states the core action but omits whether the new tab becomes focused, what it returns (tab ID?), synchronization behavior, or error handling on invalid URLs.

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?

Excellent efficiency: single sentence, 9 words, front-loaded with action. No redundancy with schema or tool name.

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?

Adequate for a single-parameter tool but incomplete given the rich browser automation context. Lacks expected details about return values, tab focus behavior, and session state changes that would compensate for missing output schema and annotations.

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 has 100% description coverage ('URL to navigate to in the new tab'), establishing baseline 3. The description adds minimal semantic value beyond the schema, only confirming optionality via 'optionally'.

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 'Open' with specific resource 'new browser tab'. The phrase 'new' implicitly distinguishes from sibling tools like pilot_navigate (current tab), pilot_tab_select (existing tabs), and pilot_tab_close, though explicit differentiation is absent.

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?

No guidance on when to use this versus pilot_navigate (navigation in current tab) or pilot_tab_select (switching to existing tabs). Despite numerous sibling alternatives, the description provides no selection criteria.

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