Skip to main content
Glama
pvinis
by pvinis

playwright_go_back

Simulate browser back button functionality to navigate to the previous page in the browsing history using Playwright MCP Server.

Instructions

Navigate back in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The GoBackTool class implements the core logic for the 'playwright_go_back' tool by calling page.goBack() on the Playwright page instance.
    export class GoBackTool extends BrowserToolBase {
      /**
       * Execute the go back tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          await page.goBack();
          return createSuccessResponse("Navigated back in browser history");
        });
      }
    }
  • The input schema definition for the 'playwright_go_back' tool, specifying no required parameters.
    {
      name: "playwright_go_back",
      description: "Navigate back in browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registration and dispatch in the main tool handler switch statement, routing calls to the GoBackTool instance.
    case "playwright_go_back":
      return await goBackTool.execute(args, context);
  • Instantiation of the GoBackTool instance during tool initialization.
    if (!goBackTool) goBackTool = new GoBackTool(server);
  • Import of the GoBackTool class from its implementation file.
    import { GoBackTool, GoForwardTool } from "./tools/browser/navigation.js";
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 'Navigate back in browser history' implies a read-only navigation action, it doesn't specify what happens if there's no history to go back to, whether it waits for page loads, or if it returns any status/error information. More behavioral context would be helpful.

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 perfectly concise at just 4 words, front-loading the essential action and resource. Every word earns its place with zero waste or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple navigation tool with no parameters and no output schema, the description is minimally adequate but lacks important context. It doesn't explain what the tool returns (success/failure indication, new page state), error conditions, or dependencies on browser session state. Given the simplicity of the tool, it's passable but could be more complete.

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 with 100% schema description coverage, so the schema fully documents the absence of parameters. The description appropriately doesn't mention any parameters, which is correct for a parameterless tool. A baseline of 4 is appropriate since no parameter information is needed.

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 resource ('browser history'), making the purpose immediately understandable. However, it doesn't explicitly distinguish this from its sibling 'playwright_go_forward', which would be helpful for 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. It doesn't mention prerequisites (like needing an active browser session), limitations (how far back it can go), or when to choose this over other navigation methods like 'playwright_navigate'.

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

Related 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/pvinis/mcp-playwright-stealth'

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