Skip to main content
Glama

browser_navigate

Automate web browser navigation to any URL. Input a URL and the tool directs the browser to load that page, enabling subsequent interactions.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to

Implementation Reference

  • Handler implementation for browser_navigate tool - uses stateManager.getDriver() to get the Selenium WebDriver and calls driver.get(url) to navigate to a URL.
    server.tool(
      'browser_navigate',
      'Navigate to a URL',
      {
        url: z.string().describe('URL to navigate to'),
      },
      async ({ url }) => {
        try {
          const driver = stateManager.getDriver();
          await driver.get(url);
          return {
            content: [{ type: 'text', text: `Navigated to ${url}` }],
          };
        } catch (e) {
          return {
            content: [{ type: 'text', text: `Error navigating: ${(e as Error).message}` }],
          };
        }
      }
    );
  • Input schema for browser_navigate tool - expects a single 'url' parameter of type string.
    {
      url: z.string().describe('URL to navigate to'),
    },
  • The registerBrowserTools function is where browser_navigate is registered as a tool on the MCP server via server.tool().
    export function registerBrowserTools(server: McpServer, stateManager: StateManager) {
      server.tool(
        'browser_open',
  • The registerAllTools function is called by the server initialization and invokes registerBrowserTools which registers browser_navigate.
    export function registerAllTools(server: McpServer, stateManager: StateManager): void {
      registerBrowserTools(server, stateManager);
      registerElementTools(server, stateManager);
      registerActionTools(server, stateManager);
      registerCookieTools(server, stateManager);
    }
  • StateManager.getDriver() is the helper method used by browser_navigate to retrieve the active Selenium WebDriver session for navigation.
    getDriver(): WebDriver {
      if (!this.state.currentSession) {
        throw new Error('No active browser session');
      }
      const driver = this.state.drivers.get(this.state.currentSession);
      if (!driver) {
        throw new Error('No active browser session');
      }
      return driver;
    }
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only says 'navigate' without explaining whether it waits for page load, handles errors, or affects browser state. Essential behavioral details are missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief (4 words), which is concise but sacrifices necessary detail. It could include more information without becoming verbose.

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 single parameter, lack of output schema, and many similar siblings, the description is insufficient. It omits behaviors like page load waiting, error handling, and navigation semantics, leaving the agent underinformed.

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 already describes the 'url' parameter adequately (100% coverage). The description adds no additional meaning beyond what the schema provides, so baseline 3 is appropriate.

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 clearly identifies the action (navigate) and the resource (URL). However, it does not differentiate from sibling tools like browser_open or browser_navigate_back/forward, which also involve navigation.

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 is provided on when to use this tool versus its many navigation-related siblings. There is no mention of prerequisites, alternatives, or exclusions.

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/pshivapr/selenium-mcp'

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