Skip to main content
Glama
BrowserGenie

BrowserGenie MCP Server

by BrowserGenie

new_tab

Open a new browser tab and optionally navigate to a URL. Returns a tab ID for further interaction.

Instructions

Open a brand new browser tab. You can optionally provide a URL to navigate to immediately. Returns the new tab ID so you can interact with it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOptional URL to load in the new tab (e.g., "https://google.com")
apiKeyNoAPI key for authentication if enabled

Implementation Reference

  • Handler function for the 'new_tab' tool. Sends a 'new_tab' command via WebSocket bridge with an optional URL parameter, and returns the result (new tab ID).
      async ({ url, apiKey }) => {
        const result = await bridge.sendCommand({
          command: 'new_tab',
          params: { url },
          apiKey,
        });
        if (!result.success) {
          return { content: [{ type: 'text', text: `Error: ${result.error?.message}` }], isError: true };
        }
        return { content: [{ type: 'text', text: JSON.stringify(result.data) }] };
      }
    );
  • Registration of the 'new_tab' tool using server.tool() from the MCP SDK, with a description and Zod schema for optional 'url' and 'apiKey' parameters.
    server.tool(
      'new_tab',
      'Open a brand new browser tab. You can optionally provide a URL to navigate to immediately. Returns the new tab ID so you can interact with it.',
      {
        url: z.string().optional().describe('Optional URL to load in the new tab (e.g., "https://google.com")'),
        apiKey: z.string().optional().describe('API key for authentication if enabled'),
      },
      async ({ url, apiKey }) => {
        const result = await bridge.sendCommand({
          command: 'new_tab',
          params: { url },
          apiKey,
        });
        if (!result.success) {
          return { content: [{ type: 'text', text: `Error: ${result.error?.message}` }], isError: true };
        }
        return { content: [{ type: 'text', text: JSON.stringify(result.data) }] };
      }
    );
  • Zod schema for the 'new_tab' tool input: optional URL string and optional API key string.
    {
      url: z.string().optional().describe('Optional URL to load in the new tab (e.g., "https://google.com")'),
      apiKey: z.string().optional().describe('API key for authentication if enabled'),
    },
Behavior3/5

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

No annotations provided, so description carries behavioral burden. It states creation and return of ID but does not mention side effects like focus changes or limitations. Adequate but not detailed.

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?

Two sentences, front-loaded with verb, no fluff. Every sentence adds value.

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?

Low complexity tool with no output schema. Description covers purpose, parameters, and return value. Sufficiently complete for its simplicity.

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%, so baseline 3. The description adds context about optional URL and return value but adds little beyond schema which already has descriptions for both parameters.

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 clearly states it opens a new browser tab and optionally navigates to a URL, with a return of tab ID. This distinguishes it from other tab-related siblings like close_tab, list_tabs, and select_tab.

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

Usage Guidelines4/5

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

The description implies when to use (need a new tab, optionally navigate) but does not explicitly state when not to use or alternatives. It is clear enough for a simple tool.

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/BrowserGenie/mcp'

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