Skip to main content
Glama

playwright_go_forward

Navigate forward in browser history to revisit previously viewed pages. Use this tool in browser automation workflows for efficient web navigation tasks.

Instructions

Navigate forward in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The GoForwardTool class implements the core logic for the playwright_go_forward tool by invoking 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's metadata including name, description, and input schema (empty as no parameters required).
      name: "playwright_go_forward",
      description: "Navigate forward in browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registers the tool handler by dispatching calls to the GoForwardTool instance in the main tool switch statement.
    case "playwright_go_forward":
      return await goForwardTool.execute(args, context);
  • Instantiates the GoForwardTool instance for use in handling tool calls.
    if (!goForwardTool) goForwardTool = new GoForwardTool(server);
  • src/tools.ts:468-468 (registration)
    Includes the tool in the BROWSER_TOOLS array, which determines browser launch requirements.
    "playwright_go_forward",
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 mentions navigation but doesn't specify what happens if there's no forward history, error conditions, or side effects. This leaves significant gaps for a tool that interacts with browser state.

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 no wasted words. It's front-loaded with the core functionality and appropriately sized for a simple navigation tool.

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 and no output schema, the description should provide more context about what happens after navigation (success/failure indicators, page state changes). As a browser interaction tool with potential side effects, the current description is insufficient for complete understanding.

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 with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this case.

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, which keeps it from a perfect score.

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 on when to use this tool versus alternatives like 'playwright_navigate' or 'playwright_go_back'. The description only states what it does, not the context or prerequisites for its use.

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

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