Skip to main content
Glama

browser_navigate

Destructive

Navigate web pages to specified URLs for automated browser interaction and content access.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • Handler function that ensures a tab exists, navigates to the provided URL, includes a snapshot in the response, and adds the equivalent Playwright code snippet.
    handle: async (context, params, response) => {
      const tab = await context.ensureTab();
      await tab.navigate(params.url);
    
      response.setIncludeSnapshot();
      response.addCode(`await page.goto('${params.url}');`);
    },
  • Tool schema defining the name 'browser_navigate', input with 'url' string parameter, marked as destructive.
    schema: {
      name: 'browser_navigate',
      title: 'Navigate to a URL',
      description: 'Navigate to a URL',
      inputSchema: z.object({
        url: z.string().describe('The URL to navigate to'),
      }),
      type: 'destructive',
    },
  • src/tools.ts:36-52 (registration)
    Registration of all tools in allTools array by importing and spreading modules including navigate.ts which defines browser_navigate.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
  • BrowserServerBackend constructor loads the filtered list of tools from tools.ts, registering browser_navigate among others for the MCP server.
    this._tools = filteredTools(config);
Behavior3/5

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

The description doesn't add behavioral details beyond what annotations provide. Annotations indicate destructiveHint=true and readOnlyHint=false, implying this is a write operation that changes browser state, which aligns with 'navigate'. However, the description lacks context like potential side effects (e.g., page reload, navigation blocking) or rate limits. No contradiction with annotations exists.

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's front-loaded and directly conveys the core action without unnecessary elaboration, 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 destructive potential) and rich annotations (destructiveHint, openWorldHint), the description is minimally adequate. However, with no output schema and the description lacking details on return values or error conditions, there are gaps in completeness for effective agent 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 'url' parameter fully documented. The description adds no additional meaning beyond the schema, such as URL format requirements or validation rules. Baseline score of 3 is appropriate since the schema carries the full burden of parameter documentation.

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 verb ('navigate') and resource ('URL'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like browser_navigate_back or browser_navigate_forward, which are related navigation actions but with different specific behaviors.

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 sibling tools like browser_navigate_back for backward navigation or browser_tab_new for opening new tabs, nor does it specify prerequisites such as needing an active browser session. Usage context is implied but not stated.

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/maywzh/playwright-mcp'

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