Skip to main content
Glama
jomon003

PlayMCP Browser Automation Server

by jomon003

goForward

Navigate forward to the next page in browser history during web automation tasks, enabling sequential page browsing for testing or data collection workflows.

Instructions

Navigate forward to the next page in history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function in PlaywrightController that executes the browser forward navigation using page.goForward() with error handling.
    async goForward(): Promise<void> {
      try {
        if (!this.isInitialized() || !this.state.page) {
          throw new Error('Browser not initialized');
        }
        this.log('Going forward');
        await this.state.page.goForward();
        this.log('Forward navigation complete');
      } catch (error: any) {
        console.error('Go forward error:', error);
        throw new BrowserError('Failed to go forward', 'Check if there is a next page in history');
      }
    }
  • Tool schema definition for goForward, specifying no input parameters are required.
    const GO_FORWARD_TOOL: Tool = {
      name: "goForward",
      description: "Navigate forward to the next page in history",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    };
  • src/server.ts:535-535 (registration)
    Registration of the goForward tool in the tools object provided to the MCP server capabilities.
    goForward: GO_FORWARD_TOOL,
  • Dispatch logic in the MCP callTool request handler that invokes the controller's goForward method and returns success response.
    case 'goForward': {
      await playwrightController.goForward();
      return {
        content: [{ type: "text", text: "Navigated forward successfully" }]
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without behavioral details. It doesn't mention what happens if there's no forward history (error? no-op?), whether this waits for page load, or any side effects. For a navigation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 perfectly front-loaded with the essential information and earns its place completely.

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 behavioral transparency gaps, it doesn't provide complete context about error conditions, waiting behavior, or integration with the browser session management implied by sibling tools.

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 schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, earning a baseline 4 for not adding unnecessary parameter information.

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 specific action ('Navigate forward') and the target resource ('next page in history'), making the purpose immediately understandable. It distinguishes itself from siblings like 'navigate' (which goes to a URL) and 'goBack' (implied sibling) by specifying forward navigation in browser history.

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 (when there's forward navigation available in browser history) but doesn't explicitly state when NOT to use it or name alternatives. It doesn't mention prerequisites like requiring a browser session or having forward history available, which would be helpful for complete guidance.

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/jomon003/PlayMCP'

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