Skip to main content
Glama

navigate

Perform browser navigation by directing to a specified URL, optionally waiting for the page to fully load. Enables automated web interactions via the MCP Browser Server.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to
waitForLoadNoWait for page to fully load

Implementation Reference

  • The main handler function for the 'navigate' tool. It validates input with NavigateSchema, navigates the current page to the specified URL using Playwright's goto method (with optional networkidle wait), retrieves the page title, and returns a success message.
    case 'navigate': {
      if (!currentPage) {
        throw new Error('No browser page available. Launch a browser first.');
      }
    
      const params = NavigateSchema.parse(args);
      
      if (params.waitForLoad) {
        await currentPage.goto(params.url, { waitUntil: 'networkidle' });
      } else {
        await currentPage.goto(params.url);
      }
    
      const title = await currentPage.title();
      
      return {
        content: [
          {
            type: 'text',
            text: `Navigated to ${params.url}\nPage title: ${title}`
          }
        ]
      };
    }
  • Zod schema defining the input parameters for the navigate tool: required URL (validated as string URL) and optional waitForLoad boolean.
    const NavigateSchema = z.object({
      url: z.string().url(),
      waitForLoad: z.boolean().default(true)
    });
  • src/index.ts:158-176 (registration)
    Registration of the 'navigate' tool in the ListTools response, including name, description, and input schema for MCP protocol compliance.
    {
      name: 'navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL to navigate to'
          },
          waitForLoad: {
            type: 'boolean',
            default: true,
            description: 'Wait for page to fully load'
          }
        },
        required: ['url']
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Navigate to a URL' implies a state-changing operation (browser navigation), but it doesn't describe what happens on failure, whether it follows redirects, or if it respects browser settings. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 a single, efficient sentence with zero wasted words. It is front-loaded with the core action ('Navigate to a URL'), making it immediately scannable. Every word earns its place, and there is no redundancy or unnecessary elaboration.

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 with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't cover what happens on success/failure, return values, or interaction with sibling tools like 'launch_browser'. For a mutation tool in a browser automation context, this leaves significant gaps for the agent.

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 both parameters ('url' and 'waitForLoad'). The description adds no parameter-specific information beyond what's in the schema. According to guidelines, baseline is 3 when schema coverage is high (>80%) and description adds no param details.

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 action (navigate) and resource (URL), making the purpose immediately understandable. It distinguishes from siblings like 'click_element' or 'scroll' by focusing on URL navigation rather than page interaction. However, it doesn't specify if this opens a new tab/window or reuses existing context, which prevents 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 doesn't mention prerequisites (e.g., needing an active browser session from 'launch_browser'), nor does it differentiate from similar actions like using 'evaluate_javascript' for navigation. Without usage context, the agent must infer when this tool is appropriate.

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/Wladastic/mcp-browser-server'

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