Skip to main content
Glama

browser_navigate_back

Navigate to the previous page in the browser history during automated web interactions. Use this tool to go back to prior web pages when testing or automating browser workflows.

Instructions

Navigate back in the browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler and registration for the 'browser_navigate_back' tool. Retrieves the browser driver and executes navigate().back() to go back in the browser history, with error handling.
    server.tool('browser_navigate_back', 'Navigate back in the browser', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        await driver.navigate().back();
        return {
          content: [{ type: 'text', text: `Navigated back` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error navigating back: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • src/tools/index.ts:9-9 (registration)
    Calls registerBrowserTools which registers the browser_navigate_back tool among others.
    registerBrowserTools(server, stateManager);
  • src/server.ts:55-55 (registration)
    Top-level call to registerAllTools, which indirectly registers the browser_navigate_back tool.
    registerAllTools(this.server, this.stateManager);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but doesn't explain what happens if there's no history to navigate back to, whether it's synchronous or asynchronous, or any error conditions. This leaves significant gaps for a mutation-like operation.

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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 that this is a mutation tool (navigating implies changing state) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or dependencies on browser session state, which are critical for safe usage.

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, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter information, so it meets the baseline expectation for a parameterless tool by not introducing confusion.

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 back') and the resource ('in the browser'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'browser_navigate_forward' beyond the directional implication, which is why it doesn't reach 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?

The description provides no guidance on when to use this tool versus alternatives like 'browser_navigate_forward' or 'browser_navigate'. It lacks context about prerequisites (e.g., whether a browser session must be active) or limitations (e.g., only works if there's history to go back to).

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