Skip to main content
Glama
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare

browser_navigate_forward

Read-only

Navigate forward to the next page in a web browser using automated browser testing with Playwright and Cloudflare Workers integration, enabling AI assistants to control browser actions.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler logic for the 'browser_navigate_forward' tool. It retrieves the current tab and executes page.goForward() to navigate forward in the browser history.
    handle: async context => {
      const tab = context.currentTabOrDie();
      await tab.page.goForward();
      const code = [
        `// Navigate forward`,
        `await page.goForward();`,
      ];
      return {
        code,
        captureSnapshot,
        waitForNetwork: false,
      };
    },
  • Input schema and metadata for the 'browser_navigate_forward' tool, defined using Zod. No parameters required.
    schema: {
      name: 'browser_navigate_forward',
      title: 'Go forward',
      description: 'Go forward to the next page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • src/tools.ts:35-50 (registration)
    Registers the browser_navigate_forward tool (via spread of navigate(true)) in the snapshotTools array for standard mode.
    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)
    Registers the browser_navigate_forward tool (via spread of navigate(false)) in the visionTools array for vision mode.
    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),
    ];
  • Final registration of tools including browser_navigate_forward into the MCP server context based on config.vision, filtering by capabilities.
    const allTools = config.vision ? visionTools : snapshotTools;
    const tools = allTools.filter(tool => !config.capabilities || tool.capability === 'core' || config.capabilities.includes(tool.capability));
    const context = new Context(tools, config, browserContextFactory);
Behavior3/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds minimal behavioral context about moving to 'the next page' in browser history, but doesn't disclose what happens if no forward history exists, error conditions, or interaction effects. No contradiction with annotations.

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?

Extremely concise single sentence with zero wasted words. The description is front-loaded with the core action ('Go forward') and efficiently completes the thought with purpose ('to the next page').

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 simplicity (0 parameters, no output schema) and comprehensive annotations, the description is minimally adequate. However, for a browser navigation tool, it lacks context about failure modes (e.g., no forward history), success indicators, or relationship to browser state management.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on the tool's action.

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 ('Go forward') and target ('to the next page'), providing a specific verb+resource combination. It distinguishes from sibling 'browser_navigate_back' by specifying forward direction, though it doesn't explicitly differentiate from all navigation-related siblings like 'browser_navigate'.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., having browser history to go forward to), when-not conditions, or explicit alternatives like 'browser_navigate' for direct URL navigation.

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

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