Skip to main content
Glama

browser_navigate_forward

Navigate forward in the browser to return to the next page in the browsing history after using the back button.

Instructions

Navigate forward in the browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and inline handler for the 'browser_navigate_forward' tool. It retrieves the current WebDriver instance from the state manager and calls navigate().forward() to navigate forward in the browser history, returning a success or error message.
    server.tool('browser_navigate_forward', 'Navigate forward in the browser', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        await driver.navigate().forward();
        return {
          content: [{ type: 'text', text: `Navigated forward` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error navigating forward: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • StateManager.getDriver() method used by the tool handler to retrieve the current WebDriver instance for navigation.
    getDriver(): WebDriver {
      if (!this.state.currentSession) {
        throw new Error('No active browser session');
      }
      const driver = this.state.drivers.get(this.state.currentSession);
      if (!driver) {
        throw new Error('No active browser session');
      }
      return driver;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like whether it waits for page load, handles errors if no forward history exists, or requires the browser to be in a specific state. The description is minimal and lacks operational context.

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 front-loaded and directly states the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 is incomplete for a browser navigation tool. It lacks details on behavior (e.g., success/failure conditions, return values), making it insufficient for an agent to understand operational nuances beyond the basic action.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, aligning with the schema's completeness. A baseline of 4 is applied since no parameters exist.

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 resource ('in the browser'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish from its sibling 'browser_navigate_back' beyond the directional difference implied by 'forward'.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., having navigated back previously), nor does it contrast with other navigation methods like 'browser_navigate' or 'browser_get_url'.

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/pshivapr/selenium-mcp'

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