Skip to main content
Glama

browser_navigate

Destructive

Navigate web browsers to specific URLs using Playwright automation, enabling programmatic web page interaction through structured accessibility snapshots.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The core handler function for the 'browser_navigate' tool. It ensures an active tab, navigates to the provided URL, generates a corresponding Playwright code snippet, and instructs to capture a snapshot without waiting for network events.
    handle: async (context, params) => {
      const tab = await context.ensureTab();
      await tab.navigate(params.url);
    
      const code = [
        `// Navigate to ${params.url}`,
        `await page.goto('${params.url}');`,
      ];
    
      return {
        code,
        captureSnapshot,
        waitForNetwork: false,
      };
    },
  • Schema definition for the 'browser_navigate' tool, specifying the name, title, description, Zod input schema (url: string), and destructive type.
      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',
    },
  • Module-level registration exporting a factory function that creates and returns the browser_navigate tool (along with back/forward) based on captureSnapshot parameter.
    export default (captureSnapshot: boolean) => [
      navigate(captureSnapshot),
      goBack(captureSnapshot),
      goForward(captureSnapshot),
    ];
  • src/tools.ts:35-50 (registration)
    Registers the navigate tool factory into the snapshotTools array via spread operator ...navigate(true), collecting all core tools.
    export const snapshotTools: Tool<any>[] = [
      ...common(true),
      ...console,
      ...dialogs(true),
      ...files(true),
      ...install,
      ...keyboard(true),
      ...navigate(true),
      ...network,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs(true),
      ...testing,
      ...wait(true),
    ];
  • src/server.ts:20-23 (registration)
    In the Server constructor, selects and filters tools from snapshotTools/visionTools (including browser_navigate) and assigns to this.tools for MCP tool listing and calling.
    constructor(config: FullConfig) {
      this.config = config;
      const allTools = config.vision ? visionTools : snapshotTools;
      this.tools = allTools.filter(tool => !config.capabilities || tool.capability === 'core' || config.capabilities.includes(tool.capability));
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description adds value by implying a navigation action that changes browser state. It doesn't contradict annotations, and while it doesn't detail side effects like page loading or potential errors, it provides basic behavioral context beyond the structured hints.

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 with a single, clear sentence: 'Navigate to a URL'. It's front-loaded with the core action and wastes no words, making it easy to parse quickly.

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?

For a tool with one parameter, high schema coverage, and annotations covering safety (destructive) and scope (openWorld), the description is minimally adequate. However, it lacks details on output (no schema), error handling, or interaction with sibling tools, leaving gaps in full contextual 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?

The schema has 100% description coverage, with the 'url' parameter fully documented. The description adds no additional meaning about the URL parameter beyond what the schema provides, such as format requirements or examples. The baseline score of 3 is appropriate given the 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 'Navigate to a URL' clearly states the action (navigate) and target (URL), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'browser_navigate_back' or explain what 'navigate' entails beyond the basic verb.

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 open browser), compare to 'browser_navigate_back', or specify scenarios where navigation is appropriate versus other browser actions like clicking or typing.

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/manishamishraacc/mcp'

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