Skip to main content
Glama

playwright_go_forward

Navigate forward in browser history during automated testing with Playwright. Use this tool to simulate user clicks on the forward button for browser automation workflows.

Instructions

Navigate forward in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The GoForwardTool class that implements the core logic of the playwright_go_forward tool by calling page.goForward() on the Playwright page instance.
    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");
        });
      }
    }
  • The input schema and metadata definition for the playwright_go_forward tool.
      name: "playwright_go_forward",
      description: "Navigate forward in browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registration in the main tool handler switch statement, dispatching execution to the GoForwardTool instance.
    case "playwright_go_forward":
      return await goForwardTool.execute(args, context);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action but doesn't mention potential side effects (e.g., page reload, navigation state changes), error conditions (e.g., what happens if no forward history exists), or performance characteristics. This leaves significant behavioral gaps for a navigation operation.

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 that communicates the core functionality without any wasted words. It's appropriately sized for a simple navigation tool and front-loads the essential information.

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 no annotations, no output schema, and a simple but potentially state-changing operation, the description is insufficient. It doesn't explain what happens on success/failure, what the return value might be, or how this interacts with other navigation tools. For a browser history navigation tool, more context about behavior and outcomes is needed.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and it doesn't need to compensate for any schema gaps.

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 ('Navigate forward') and target ('in browser history'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'playwright_go_back' beyond the directional implication, missing explicit sibling comparison.

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 like 'playwright_navigate' or 'playwright_go_back'. The description only states what it does, not when it's appropriate or what prerequisites might exist (e.g., requiring browser history to have forward pages available).

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

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