Playwright MCP Server

by devskido

Overview Schema Source Related Servers Discussions Admin

TypeScript

playwright_go_forward

Navigate forward in browser history to revisit previously viewed pages during web automation tasks.

Instructions

Navigate forward in browser history

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/browser/navigation.ts:111-121 (handler)

GoForwardTool class implements the core logic for the playwright_go_forward tool by calling page.goForward() on the Playwright page object.

export class GoForwardTool extends BrowserToolBase {
  /**
   * Execute the go forward tool
   */
  async execute(args: any, context: ToolContext): Promise<ToolResponse> {
    return this.safeExecute(context, async (page) => {
      await page.goForward();
      return createSuccessResponse("Navigated forward in browser history");
    });
  }
}

src/tools.ts:378-386 (schema)

Input schema definition for the playwright_go_forward tool, specifying no required parameters.

{
  name: "playwright_go_forward",
  description: "Navigate forward in browser history",
  inputSchema: {
    type: "object",
    properties: {},
    required: [],
  },
},

src/toolHandler.ts:541-543 (registration)
Switch case in handleToolCall that registers and dispatches the playwright_go_forward tool call to GoForwardTool.execute.
```
  return await goBackTool.execute(args, context);
case "playwright_go_forward":
  return await goForwardTool.execute(args, context);
```

src/toolHandler.ts:343-344 (registration)

Initialization of the GoForwardTool instance in initializeTools function.

if (!goBackTool) goBackTool = new GoBackTool(server);
if (!goForwardTool) goForwardTool = new GoForwardTool(server);

src/tools.ts:467-468 (registration)
Inclusion of playwright_go_forward in the BROWSER_TOOLS array for conditional browser launching.
```
"playwright_go_back",
"playwright_go_forward",
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided, so the description carries full burden. It only restates the tool's name and lacks disclosure about edge cases (e.g., behavior when at the latest page or if history is empty).

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?

A single sentence is highly concise and front-loaded with the core action. Every word earns its place; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple action with no parameters or output schema, the description captures the essential purpose. However, it lacks details about edge cases (e.g., if no forward history exists), slightly reducing completeness.

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?

No parameters are defined, and schema coverage is 100%. The description adds no parameter information, but that is acceptable given zero parameters; baseline 4 is appropriate.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'navigate' and the resource 'forward in browser history', making the tool's purpose immediately understandable. It distinguishes itself from siblings like 'playwright_go_back'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives (e.g., navigating via URL or clicking a link). Usage is implied as a standard browser history forward action, but no exclusions or context are provided.

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