Skip to main content
Glama

browser_navigate

Directs a browser to a specified URL using Playwright sessions, enabling automated web navigation within isolated browser instances managed by the server.

Instructions

Navigate to URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes

Implementation Reference

  • index.js:301-315 (registration)
    Registration of the 'browser_navigate' tool using server.tool, which proxies the call to a browser client.
    server.tool('browser_navigate', 'Navigate to URL', { url: z.string() },
      async (args, extra) => {
        log(`[browser_navigate] called with args: ${JSON.stringify(args)}`);
        try {
          const result = await proxyToolCall('browser_navigate', args);
          log(`[browser_navigate] result: ${JSON.stringify(result).slice(0, 500)}`);
          if (!result.isError) {
            hasActivePage = true; // Mark page as active after successful navigation
          }
          return result;
        } catch (err) {
          log(`[browser_navigate] ERROR: ${err.message}\n${err.stack}`);
          throw err;
        }
      });
  • The proxyToolCall function serves as the actual implementation handler that forwards tool execution requests (including 'browser_navigate') to the underlying MCP client.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
        log(`[proxyToolCall] Result type: ${typeof result}`);
        log(`[proxyToolCall] Result: ${JSON.stringify(result).slice(0, 500)}`);
    
        // The SDK returns { content: [...], isError?: boolean }
        // We need to return this same format
        if (result && result.content) {
          return result;
        }
    
        // Fallback: wrap in content array if needed
        return {
          content: [{ type: 'text', text: JSON.stringify(result) }]
        };
      } catch (error) {
        log(`[proxyToolCall] ERROR: ${error.message}\n${error.stack}`);
        return {
          content: [{ type: 'text', text: `Error: ${error.message}` }],
          isError: true
        };
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden but offers none. It does not state whether the tool waits for page load completion, how it handles redirects, authentication dialogs, or invalid URLs.

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 three-word description is concise and front-loaded with no wasted text. However, brevity crosses into under-specification given the lack of schema documentation and behavioral details.

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?

For a single-parameter tool with 0% schema coverage, the description fails to explain the parameter's semantics or expected values. It also omits critical browser automation context such as page lifecycle behavior, error states, or side effects on the browser session.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (url parameter has no description). The description mentions 'URL' but does not compensate for the schema gap by explaining required format (absolute vs relative), supported protocols (http:, https:, file:), or validation rules.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Navigate to URL' restates the tool name (browser_navigate) with minimal elaboration. It fails to distinguish from sibling tool browser_navigate_back, which also performs navigation but presumably uses history rather than a fresh URL.

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 provided on when to use this versus browser_navigate_back or other navigation methods. No mention of prerequisites like having an open browser context or valid URL format.

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/OMGEverdo/browser-pool-mcp'

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