Skip to main content
Glama
pvinis
by pvinis

playwright_go_forward

Navigate forward in browser history to revisit previously viewed pages within Playwright MCP Server's real browser environment, enabling continuous web interaction and testing.

Instructions

Navigate forward in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The GoForwardTool class provides the core handler logic for the 'playwright_go_forward' tool, executing 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");
        });
      }
    } 
  • Defines the tool name, description, and input schema (no required parameters) for 'playwright_go_forward'.
    {
      name: "playwright_go_forward",
      description: "Navigate forward in browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registers and dispatches the 'playwright_go_forward' tool call to the GoForwardTool instance's execute method in the main tool handling switch statement.
    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. While 'Navigate forward in browser history' implies a read-only operation that moves through existing history, it doesn't specify what happens if there's no forward history available, whether this requires a specific browser context, or what the expected outcome is. For a navigation tool with zero annotation coverage, this is insufficient.

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 function without any wasted words. It's appropriately sized for a simple navigation tool and gets straight to the point.

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?

For a simple navigation tool with no parameters and no output schema, the description covers the basic purpose adequately. However, given the lack of annotations and the fact this is part of a browser automation suite with many sibling tools, more context about when this is appropriate versus other navigation methods would be helpful. The description meets minimum viable standards but could be more complete.

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 zero parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description appropriately doesn't discuss parameters since none exist, which is correct for this case. No additional parameter information is needed or provided.

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 verb ('Navigate forward') and resource ('in browser history'), making the tool's function immediately understandable. It doesn't explicitly differentiate from its sibling 'playwright_go_back', but the distinction is obvious from the directional terms 'forward' vs 'back'.

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 about when to use this tool versus alternatives like 'playwright_navigate' or 'playwright_get', nor does it mention prerequisites like requiring an existing browser session with navigation history. It simply states what the tool does without contextual usage information.

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

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