Skip to main content
Glama
devskido

Playwright MCP Server

by devskido

playwright_go_back

Navigate back in browser history during web automation tasks to return to previous pages.

Instructions

Navigate back in browser history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • GoBackTool class implementing the execute method for playwright_go_back tool, which calls page.goBack()
    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");
        });
      }
    }
  • Tool schema definition including name, description, and empty input schema for playwright_go_back
      name: "playwright_go_back",
      description: "Navigate back in browser history",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Registration in the main tool handler switch case, dispatching to goBackTool.execute
    case "playwright_go_back":
      return await goBackTool.execute(args, context);
  • Instantiation of the goBackTool instance during tool initialization
    if (!goBackTool) goBackTool = new GoBackTool(server);
  • src/tools.ts:467-467 (registration)
    Inclusion in BROWSER_TOOLS array for conditional browser launching
    "playwright_go_back",
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Navigate back' implies a navigation action, it doesn't specify whether this requires an existing browser context, what happens if there's no history to go back to, or any error conditions. This leaves significant behavioral gaps for a tool that likely interacts with browser state.

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 that directly states the tool's function without any unnecessary words. It's perfectly front-loaded and wastes no space, making it ideal for quick comprehension.

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 likely complexity (browser navigation with potential state dependencies), the description is insufficient. With no annotations, no output schema, and minimal behavioral context, it doesn't provide enough information for reliable use. A better description would explain prerequisites, failure conditions, or relationship to other navigation tools.

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 fully documents the absence of inputs. The description appropriately doesn't add parameter information beyond what's already covered, earning a baseline score of 4 for this dimension.

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 'Navigate back in browser history' clearly states the verb ('Navigate back') and resource ('browser history'), making the purpose immediately understandable. However, it doesn't explicitly distinguish itself from its sibling 'playwright_go_forward', which would have earned 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 'playwright_navigate' or 'playwright_go_forward'. It lacks any context about prerequisites (e.g., requiring an active browser session) or typical use cases, leaving the agent with minimal usage direction.

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/devskido/customed-playwright'

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