Skip to main content
Glama

browser_navigate

Direct a browser to navigate to a specified URL, set navigation timeouts, and wait for specific page load criteria like 'load' or 'domcontentloaded' for precise control.

Instructions

Navigate to a specific URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNoNavigation timeout in milliseconds
urlYesURL to navigate to
waitUntilNoNavigation wait criteria

Implementation Reference

  • Executes the browser navigation by calling page.goto with the provided URL, timeout, and waitUntil options. Returns success or error message.
    async function handleBrowserNavigate(page: Page, args: any): Promise<{ toolResult: CallToolResult }> {
      try {
        await page.goto(args.url, {
          timeout: args.timeout || 30000,
          waitUntil: args.waitUntil || "load"
        });
        return {
          toolResult: {
            content: [{
              type: "text",
              text: `Navigated to ${args.url}`,
            }],
            isError: false,
          },
        };
      } catch (error) {
        return {
          toolResult: {
            content: [{
              type: "text",
              text: `Navigation failed: ${(error as Error).message}`,
            }],
            isError: true,
          },
        };
      }
    }
  • Defines the tool name, description, and input schema requiring 'url' with optional 'timeout' and 'waitUntil' parameters.
    {
      name: "browser_navigate",
      description: "Navigate to a specific URL",
      inputSchema: {
        type: "object",
        properties: {
          url: { type: "string", description: "URL to navigate to" },
          timeout: { type: "number", description: "Navigation timeout in milliseconds" },
          waitUntil: { 
            type: "string", 
            description: "Navigation wait criteria",
            enum: ["load", "domcontentloaded", "networkidle", "commit"]
          }
        },
        required: ["url"]
      }
    },
  • Registers the dispatch for 'browser_navigate' tool calls to the specific handler function within the main executeToolCall switch statement.
    case "browser_navigate":
      return await handleBrowserNavigate(activePage!, args);
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 basic action but doesn't cover critical aspects like whether navigation is synchronous/asynchronous, error handling, browser state changes, or performance implications. This is inadequate for a tool that likely interacts with a browser environment.

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 just four words, front-loading the core purpose without any wasted text. Every word earns its place, making it efficient and easy to parse.

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 complexity of browser navigation (with 3 parameters, no annotations, and no output schema), the description is insufficient. It doesn't explain what happens after navigation, error conditions, or how it integrates with other browser tools, leaving significant gaps for agent understanding.

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 the schema fully documents all three parameters. The description doesn't add any parameter-specific information beyond what's in the schema, such as URL format requirements or waitUntil behavior details. This meets the baseline for 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 clearly states the action ('Navigate') and target ('to a specific URL'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential sibling navigation tools (though none are listed among siblings), making it clear but lacking 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, context for navigation, or differences from other browser tools like 'browser_click' or 'browser_evaluate', leaving the agent with no usage direction.

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

Related 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/imprvhub/mcp-browser-agent'

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