Skip to main content
Glama

browser_go_forward

Navigate forward to the next page in a browser instance when using the Concurrent Browser MCP server. This tool moves forward in the browsing history after going back.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceIdYesInstance ID

Implementation Reference

  • The main handler function for the 'browser_go_forward' tool. It retrieves the browser instance and calls Playwright's page.goForward() method.
    private async goForward(instanceId: string): Promise<ToolResult> {
      const instance = this.browserManager.getInstance(instanceId);
      if (!instance) {
        return { success: false, error: `Instance ${instanceId} not found` };
      }
    
      try {
        await instance.page.goForward();
        return {
          success: true,
          data: { url: instance.page.url() },
          instanceId
        };
      } catch (error) {
        return {
          success: false,
          error: `Go forward failed: ${error instanceof Error ? error.message : error}`,
          instanceId
        };
      }
    }
  • src/tools.ts:527-528 (registration)
    The switch case in executeTools that routes calls to the goForward handler.
    case 'browser_go_forward':
      return await this.goForward(args.instanceId);
  • The tool definition including name, description, and input schema, registered in getTools().
    {
      name: 'browser_go_forward',
      description: 'Go forward to the next page',
      inputSchema: {
        type: 'object',
        properties: {
          instanceId: {
            type: 'string',
            description: 'Instance ID'
          }
        },
        required: ['instanceId']
      }
    },
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 the action but doesn't explain what happens if there's no forward page available (e.g., error behavior), whether it waits for navigation to complete, or what the expected outcome is. This leaves significant behavioral gaps 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 appropriately sized for a simple navigation tool and front-loads the core functionality immediately.

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 the tool's navigation purpose and lack of both annotations and output schema, the description is insufficient. It doesn't explain what constitutes 'success' (e.g., page loaded), error conditions, or behavioral expectations, leaving the agent with incomplete context for proper usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the single 'instanceId' parameter. The description doesn't add any parameter-specific information beyond what's in the schema, maintaining the baseline score of 3 where schema does the heavy lifting.

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 tool from its sibling 'browser_go_back' (which presumably goes backward), leaving some room for sibling differentiation.

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 'browser_navigate' or 'browser_go_back', nor does it mention prerequisites (e.g., requiring a browser instance with forward navigation available). 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

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/sailaoda/concurrent-browser-mcp'

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