Playwright MCP Server

by devskido

Overview Schema Source Related Servers Discussions Admin

TypeScript

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

Name	Required	Description	Default
No arguments

Implementation Reference

src/tools/browser/navigation.ts:96-106 (handler)

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");
    });
  }
}

src/tools.ts:370-377 (schema)

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: [],
  },
},

src/toolHandler.ts:540-541 (registration)
Registration in the main tool handler switch case, dispatching to goBackTool.execute
```
case "playwright_go_back":
  return await goBackTool.execute(args, context);
```
src/toolHandler.ts:343-343 (registration)
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",
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states the basic action without disclosing preconditions (e.g., requires history), error behavior, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with only four words, no waste. However, it could be slightly more structured by including a note about precondition, but for a simple tool it is acceptable.

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?

The tool is simple with no parameters or output schema. The description adequately conveys the primary action but lacks context about prerequisites or limitations, making it minimally viable.

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?

There are no parameters, and schema coverage is 100%. The baseline of 4 is appropriate since the description does not need to add parameter semantics for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('browser history'). It is unambiguous and distinguishes itself from sibling tools like 'playwright_go_forward' and 'playwright_navigate'.

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 on when to use this tool versus alternatives. For example, it does not mention that it only works if there is a previous page, nor does it compare to 'playwright_go_forward' or 'playwright_navigate'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.