Skip to main content
Glama
devskido

Playwright MCP Server

by devskido

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
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • 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");
        });
      }
    } 
  • 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: [],
      },
    },
  • 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);
  • 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",
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like what happens if no forward history exists (e.g., error, no-op), whether it waits for page load, or if it's synchronous/asynchronous. For a navigation tool with zero annotation coverage, this is a significant gap.

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, efficient sentence ('Navigate forward in browser history') with zero waste. It's appropriately sized and front-loaded, conveying the core purpose immediately without unnecessary elaboration.

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 0 parameters, 100% schema coverage, and no output schema, the description is minimally adequate. However, as a navigation tool with no annotations, it lacks details on behavior (e.g., error handling, page load waits) that would help an agent use it correctly. It's complete for basic understanding but has clear gaps.

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 tool has 0 parameters, and schema description coverage is 100% (empty schema). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for zero-parameter tools. No additional value is required or provided.

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 'Navigate forward in browser history' clearly states the verb ('Navigate forward') and resource ('browser history'), distinguishing it from siblings like 'playwright_go_back' (backward navigation) and 'playwright_navigate' (new URL navigation). It's specific and unambiguous.

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

Usage Guidelines4/5

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

The description implies usage context (browser navigation) but doesn't explicitly state when to use this vs. alternatives like 'playwright_go_back' or 'playwright_navigate'. It's clear from the name and purpose, but lacks explicit guidance on prerequisites (e.g., requires forward history to exist).

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/devskido/customed-playwright'

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