Skip to main content
Glama
Angeluis001

Playwright MCP

by Angeluis001

browser_navigate_back

Destructive

Navigate to the previous page in the browser during web automation. Use this Playwright MCP tool to return to the prior page when interacting with web content.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that navigates the browser tab back using tab.page.goBack() and generates corresponding code snippet.
    handle: async context => {
      const tab = await context.ensureTab();
      await tab.page.goBack();
      const code = [
        `// Navigate back`,
        `await page.goBack();`,
      ];
    
      return {
        code,
        captureSnapshot,
        waitForNetwork: false,
      };
    },
  • Schema definition for the browser_navigate_back tool, specifying name, title, description, input schema, and type.
    schema: {
      name: 'browser_navigate_back',
      title: 'Go back',
      description: 'Go back to the previous page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • Registration of the browser_navigate_back tool (as goBack) in the exported array of tools.
    export default (captureSnapshot: boolean) => [
      navigate(captureSnapshot),
      goBack(captureSnapshot),
      goForward(captureSnapshot),
    ];
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, implying a state-changing operation. The description adds context by specifying it navigates to the 'previous page', which aligns with annotations and clarifies the action beyond just 'destructive'. No contradiction with annotations.

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, front-loaded sentence with zero waste. It's appropriately sized for a simple, parameterless tool and gets straight to the point.

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

Completeness4/5

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

Given the tool's simplicity (0 parameters, no output schema) and annotations covering safety (destructive), the description is complete enough. However, it could briefly mention browser state dependency or error cases for full completeness.

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?

With 0 parameters and 100% schema coverage, the baseline is 4. The description doesn't need to explain parameters, and it efficiently states the action without redundancy.

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 'Go back to the previous page' clearly states the verb ('go back') and resource ('previous page'), distinguishing it from siblings like 'browser_navigate' (forward navigation) and 'browser_tabs' (tab management). It's specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage in a browser context after navigation has occurred, but it doesn't explicitly state when not to use it or name alternatives. It provides clear context but lacks exclusions or direct sibling comparisons.

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/Angeluis001/playwright-mcp'

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