Playwright MCP

browser_navigate_forward

Read-only

Navigate forward to the next page in browser history during web automation tasks.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/navigate.ts:68-72 (handler)
The handler function for 'browser_navigate_forward' that performs the forward navigation in the browser tab using Playwright's page.goForward() method, includes a snapshot in the response, and adds the corresponding code snippet.
```
handle: async (tab, params, response) => {
  await tab.page.goForward();
  response.setIncludeSnapshot();
  response.addCode(`await page.goForward();`);
},
```
src/tools/navigate.ts:61-67 (schema)
Schema definition for the 'browser_navigate_forward' tool, specifying name, title, description, empty input schema, and readOnly type.
```
schema: {
  name: 'browser_navigate_forward',
  title: 'Go forward',
  description: 'Go forward to the next page',
  inputSchema: z.object({}),
  type: 'readOnly',
},
```
src/tools/navigate.ts:75-79 (registration)
Exports the 'browser_navigate_forward' tool (as goForward) along with others for inclusion in the central tools list.
```
export default [
  navigate,
  goBack,
  goForward,
];
```

src/tools.ts:36-52 (registration)

Central registration of all tools, spreading the navigate tools (including browser_navigate_forward) into the allTools array used by the MCP server backend.

export const allTools: Tool<any>[] = [
  ...common,
  ...console,
  ...dialogs,
  ...evaluate,
  ...files,
  ...install,
  ...keyboard,
  ...navigate,
  ...network,
  ...mouse,
  ...pdf,
  ...screenshot,
  ...snapshot,
  ...tabs,
  ...wait,
];

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.4/5.0

Behavior3/5

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

Annotations provide readOnlyHint=true, destructiveHint=false, and openWorldHint=true, indicating a safe, read-only operation with potential side effects. The description adds minimal behavioral context beyond this, as 'Go forward' implies navigation but doesn't detail effects like page loading or history changes. It doesn't contradict annotations, so it earns a baseline score for adding some 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 a single, clear sentence with zero wasted words. It's front-loaded with the core action, making it highly efficient and easy to parse. Every word earns its place by directly conveying the tool's purpose.

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 low complexity (0 parameters, no output schema) and rich annotations covering safety and behavior, the description is adequate but minimal. It states what the tool does but lacks details on usage context or expected outcomes, which could be helpful for an agent. It meets minimum viability without being comprehensive.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate. It earns a high score because it doesn't need to compensate for any schema gaps, and the lack of parameter discussion is efficient.

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. However, it doesn't explicitly distinguish itself from sibling tools like 'browser_navigate_back' or 'browser_navigate', though the action is inherently different. The purpose is unambiguous but lacks sibling differentiation.

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 like 'browser_navigate_back' or 'browser_navigate'. It doesn't mention prerequisites (e.g., requiring a browser session or forward history), exclusions, or contextual cues. Usage is implied by the action but not explicitly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.