Skip to main content
Glama

go_forward

Navigate to the next page in browser automation workflows. Use this tool to advance forward through web page history during automated browsing sessions.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'go_forward' MCP tool object, including name, description, input schema, and inline handler function within the createPlaywrightTools array
    {
      name: 'go_forward',
      description: 'Go forward to the next page',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
      handler: async () => {
        await browser.goForward();
        return { success: true, message: 'Went forward to next page' };
      }
    },
  • The handler function that executes the tool logic for 'go_forward', delegating to browser.goForward() and returning a success response
    handler: async () => {
      await browser.goForward();
      return { success: true, message: 'Went forward to next page' };
    }
  • Input schema for the 'go_forward' tool, specifying no required properties
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • Supporting helper method in SimpleBrowser class that ensures browser is launched and calls Playwright's page.goForward() for navigation
    async goForward() {
      await this.ensureLaunched();
      await this.page.goForward();
    }
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 'go forward' implies navigation, it doesn't specify what happens if there's no forward page (error behavior), whether this affects page state, or what the expected outcome is. The description lacks crucial behavioral context for a navigation tool.

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 with zero wasted words. It's perfectly front-loaded with the core action and target, making it immediately understandable without any unnecessary elaboration.

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?

For a navigation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'next page' means in context (browser history navigation), what happens on success/failure, or what the agent should expect after invocation. Given the complexity of navigation operations, more context 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 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 context.

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 ('go forward') and target ('to the next page'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like 'go_back' or 'navigate', which would require mentioning backward navigation or URL-based navigation respectively.

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 on when to use this tool versus alternatives like 'go_back', 'navigate', or 'reload'. There's no mention of prerequisites (e.g., needing to be on a page with forward navigation available) or typical usage contexts beyond the basic action.

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/zypin-testing/zypin-mcp'

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