Skip to main content
Glama
Angeluis001

Playwright MCP

by Angeluis001

browser_navigate

Destructive

Navigate web browsers to specific URLs using Playwright automation, enabling programmatic web page access and interaction.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The handler function that executes the browser_navigate tool: ensures a tab, navigates to the URL, generates corresponding Playwright code, and instructs on snapshot capture.
    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,
      };
    },
  • Input schema and metadata for the browser_navigate tool using Zod validation.
    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:35-50 (registration)
    Registration of browser_navigate tool (via ...navigate(true)) in the snapshotTools array used for tool registration.
    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/tools.ts:52-66 (registration)
    Registration of browser_navigate tool (via ...navigate(false)) in the visionTools array.
    export const visionTools: Tool<any>[] = [
      ...common(false),
      ...console,
      ...dialogs(false),
      ...files(false),
      ...install,
      ...keyboard(false),
      ...navigate(false),
      ...network,
      ...pdf,
      ...tabs(false),
      ...testing,
      ...vision,
      ...wait(false),
    ];
  • src/tools.ts:23-23 (registration)
    Import of the navigate.ts module containing the browser_navigate tool implementation.
    import navigate from './tools/navigate.js';
Behavior3/5

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

Annotations indicate destructiveHint=true and openWorldHint=true, which the description doesn't contradict. However, it adds minimal behavioral context beyond annotations—it doesn't explain what 'navigate' destroys, potential side effects, or navigation specifics. With annotations covering safety, it earns a baseline score for not adding much value.

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 no wasted words—'Navigate to a URL' is a single, clear sentence. It's front-loaded and appropriately sized for a simple tool, earning full marks for efficiency.

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 destructive potential) and lack of output schema, the description is incomplete. It doesn't explain return values, error conditions, or navigation outcomes. With annotations providing some context but no output details, it falls short of being fully informative.

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% for the single parameter 'url', so the schema fully documents it. The description doesn't add any meaning beyond the schema, such as URL format constraints or navigation behavior details. Baseline 3 is appropriate as the schema handles parameter documentation.

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

Purpose3/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), but it's vague about scope and doesn't distinguish from siblings like browser_navigate_back. It specifies the resource but lacks detail on 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, context for navigation, or compare to siblings like browser_navigate_back or browser_tabs. The description offers no usage context beyond the basic action.

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

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