Skip to main content
Glama

navigate_page

Directs a Chrome browser page to a specific URL for automation, debugging, or testing workflows. Set a timeout to control navigation wait time.

Instructions

Navigates the currently selected page to a URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate the page to
timeoutNoMaximum wait time in milliseconds. If set to 0, the default timeout will be used.

Implementation Reference

  • The handler function that executes the tool logic: gets the selected page and navigates to the provided URL using puppeteer-core's page.goto, with optional timeout.
    handler: async (request, response, context) => {
      const page = context.getSelectedPage();
    
      await context.waitForEventsAfterAction(async () => {
        await page.goto(request.params.url, {
          timeout: request.params.timeout,
        });
      });
    
      response.setIncludePages(true);
    },
  • Zod schema for input parameters: required 'url' string and optional 'timeout' number from timeoutSchema.
    schema: {
      url: z.string().describe('URL to navigate the page to'),
      ...timeoutSchema,
    },
  • src/main.ts:307-320 (registration)
    The navigate_page tool is registered by including all exports from pagesTools in the tools array, then looping to call registerTool for each, which registers it on the McpServer.
    const tools = [
      ...Object.values(consoleTools),
      ...Object.values(emulationTools),
      ...Object.values(inputTools),
      ...Object.values(networkTools),
      ...Object.values(pagesTools),
      ...Object.values(performanceTools),
      ...Object.values(screenshotTools),
      ...Object.values(scriptTools),
      ...Object.values(snapshotTools),
    ];
    for (const tool of tools) {
      registerTool(tool as unknown as ToolDefinition);
    }
Behavior3/5

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

Annotations indicate readOnlyHint=false, meaning this is a mutation tool, which aligns with 'navigates' implying a state change. The description adds context about navigating 'the currently selected page', clarifying scope, but doesn't disclose behavioral traits like whether it waits for page load, handles errors, or requires specific permissions. With annotations covering the mutation aspect, the description adds some value but lacks rich behavioral details.

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 that front-loads the core action ('Navigates the currently selected page') and purpose ('to a URL'). There is zero waste or redundancy, making it highly concise and well-structured for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (navigation with timeout), no output schema, and annotations only covering mutation status, the description is adequate but incomplete. It lacks details on return values, error handling, or interaction with sibling tools like 'select_page'. It meets minimum viability but has clear gaps in contextual guidance.

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%, with clear descriptions for both parameters: 'url' as the destination and 'timeout' as wait time with default behavior. The description mentions 'to a URL', which aligns with the 'url' parameter but adds no extra meaning beyond the schema. Baseline is 3 since the schema fully documents parameters.

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 ('navigates') and resource ('the currently selected page'), specifying it goes to a URL. It distinguishes from siblings like 'navigate_page_history' (which suggests history navigation) and 'new_page' (which creates a new page), but doesn't explicitly contrast with other navigation-related tools. The purpose is specific but could be more distinct.

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 minimal guidance: it implies usage when you need to change the page's URL. However, it doesn't specify when to use this versus alternatives like 'navigate_page_history' or 'new_page', nor does it mention prerequisites (e.g., requiring a selected page via 'select_page') or exclusions. No explicit when/when-not instructions are given.

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/SHAY5555-gif/chrome-devtools-mcp'

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