Skip to main content
Glama

browser_navigate

Directs a web browser to open a specified URL, enabling automated web navigation for testing or interaction tasks.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to

Implementation Reference

  • Handler function that retrieves the current browser driver from stateManager and navigates to the specified URL, returning success or error message.
    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 defining the 'url' parameter as a required string for the browser_navigate tool.
    {
      url: z.string().describe('URL to navigate to'),
    },
  • Direct registration of the 'browser_navigate' tool using server.tool within registerBrowserTools, specifying name, description, input schema, and inline handler function.
    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}` }],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Navigate') but lacks critical details: it doesn't specify if this requires an existing browser session, what happens on failure (e.g., invalid URL), whether it waits for page load, or any side effects like history updates. This leaves significant behavioral gaps for a navigation tool.

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 at three words, front-loading the core action without any wasted text. Every word ('Navigate', 'to', 'a URL') directly contributes to understanding the tool's function, making it efficient and well-structured for quick comprehension.

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 (navigation in a browser context with potential side effects), no annotations, and no output schema, the description is incomplete. It fails to address key contextual aspects like error handling, session requirements, or what constitutes successful navigation, leaving the agent with insufficient information for 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 single parameter 'url' documented as 'URL to navigate to'. The description adds no additional meaning beyond this, as it merely restates the parameter's purpose without clarifying format constraints (e.g., must be valid HTTP/HTTPS) or examples. This meets the baseline of 3 given the high schema coverage.

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. However, it doesn't explicitly differentiate from sibling tools like 'browser_get_url' (which retrieves the current URL) or 'browser_open' (which might open a new browser instance), missing full sibling differentiation.

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 doesn't mention prerequisites (e.g., requiring an open browser session), exclusions, or comparisons to siblings like 'browser_open' for initial navigation or 'browser_navigate_back' for history navigation, leaving usage context entirely implicit.

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