Skip to main content
Glama
epi-builder
by epi-builder

browser_navigate

Navigate web browsers to specified URLs for automated testing and interaction using Playwright MCP Server's browser automation capabilities.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The main handler function for the 'browser_navigate' tool. It ensures a browser and page are available, navigates to the specified URL using Playwright's page.goto(), and returns a confirmation message.
    private async handleNavigate(url: string) {
      await this.ensureBrowser();
      await this.browserState.page!.goto(url);
      
      return {
        content: [
          {
            type: 'text',
            text: `Navigated to ${url}`,
          },
        ],
      };
    }
  • Input schema definition for the 'browser_navigate' tool, specifying that it requires a 'url' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The URL to navigate to',
        },
      },
      required: ['url'],
    },
  • src/server.ts:60-73 (registration)
    Registration of the 'browser_navigate' tool in the list of available tools returned by ListToolsRequestHandler, including name, description, and input schema.
    {
      name: 'browser_navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The URL to navigate to',
          },
        },
        required: ['url'],
      },
    },
  • Dispatch case in the CallToolRequestHandler switch statement that routes 'browser_navigate' calls to the handleNavigate method.
    case 'browser_navigate':
      return await this.handleNavigate(args?.url as string);
  • Helper method used by browser_navigate handler to launch Chromium browser and create a new page if not already available.
    private async ensureBrowser() {
      if (!this.browserState.browser) {
        this.browserState.browser = await chromium.launch({
          headless: false,
        });
      }
      if (!this.browserState.page) {
        this.browserState.page = await this.browserState.browser.newPage();
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Navigate to a URL' implies a navigation action but fails to describe key behaviors: whether it opens a new tab or uses an existing one, if it waits for page load, error handling for invalid URLs, or any side effects (e.g., history changes). This leaves significant gaps in understanding how the tool operates beyond its basic function.

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?

The description is extremely concise and front-loaded, consisting of a single, clear sentence: 'Navigate to a URL.' Every word earns its place by directly conveying the core action, with no unnecessary elaboration or redundancy. This efficiency makes it easy for an agent to parse and understand quickly.

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

Completeness2/5

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

Given the tool's complexity (a navigation action with potential behavioral nuances) and the lack of annotations and output schema, the description is incomplete. It does not address what happens after navigation (e.g., success indicators, error responses), nor does it provide context about browser state or interactions. For a tool with no structured behavioral data, more descriptive detail is needed to ensure reliable use.

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?

The input schema has 100% description coverage, with the 'url' parameter fully documented in the schema itself. The description adds no additional meaning beyond what the schema provides—it merely restates the tool's purpose without elaborating on parameter usage, constraints, or examples. This meets the baseline score of 3, as the schema adequately covers parameter semantics.

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?

The description 'Navigate to a URL' clearly states the tool's function with a specific verb ('Navigate') and resource ('a URL'), making the purpose immediately understandable. It distinguishes itself from siblings like browser_click or browser_type by focusing on URL navigation rather than interaction or input. However, it doesn't explicitly differentiate from all siblings (e.g., browser_close might be vaguely related to navigation), so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It lacks any mention of prerequisites (e.g., needing an open browser), context for use (e.g., after browser initialization), or exclusions (e.g., not for navigating within a page). Without such information, the agent must infer usage from the tool name alone, which is insufficient for optimal tool selection.

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/epi-builder/mcp-test'

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