Skip to main content
Glama

go_back

Navigate to the previous page in browser automation workflows, enabling efficient backtracking during web navigation and interaction tasks.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'go_back'. Calls browser.goBack() and returns success response.
    handler: async () => {
      await browser.goBack();
      return { success: true, message: 'Went back to previous page' };
    }
  • Input schema for 'go_back' tool (no required parameters).
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • Full tool registration object for 'go_back' returned by createPlaywrightTools, including name, description, schema, and handler.
    {
      name: 'go_back',
      description: 'Go back to the previous page',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
      handler: async () => {
        await browser.goBack();
        return { success: true, message: 'Went back to previous page' };
      }
    },
  • Browser wrapper method goBack() that ensures browser is launched and calls Playwright page.goBack().
    async goBack() {
      await this.ensureLaunched();
      await this.page.goBack();
    }
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. 'Go back to the previous page' implies navigation but doesn't specify whether this requires an active browser session, what happens if there's no history, whether it waits for page load, or what the response looks like. 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 waste. It's appropriately sized for a simple navigation tool and front-loads the core functionality immediately. Every word earns its place in conveying the essential action.

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 address behavioral aspects like what constitutes success/failure, whether it returns the new URL, or what happens in edge cases (no history, same page). Given the sibling tools include various navigation and interaction functions, more context about this tool's specific role would be helpful.

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 schema already fully documents the parameter situation. The description appropriately doesn't mention parameters, maintaining focus on the tool's purpose. Baseline for zero parameters is 4, as there's no parameter information to add beyond what's already covered.

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 back') and target ('previous page'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'go_forward' or 'navigate' beyond the basic directional difference, which prevents 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 'go_forward', 'navigate', or 'reload'. It doesn't specify prerequisites (e.g., requires a browser session with history) or contextual constraints, leaving the agent to infer appropriate usage scenarios.

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