Skip to main content
Glama
cloudflare

Cloudflare Playwright MCP

Official
by cloudflare

browser_navigate_back

Read-only

Enables automated browser testing by navigating back to the previous page using Cloudflare Playwright MCP for seamless workflow integration and efficient web interaction.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the browser_navigate_back tool by calling goBack on the current browser page/tab.
    handle: async context => {
      const tab = await context.ensureTab();
      await tab.page.goBack();
      const code = [
        `// Navigate back`,
        `await page.goBack();`,
      ];
    
      return {
        code,
        captureSnapshot,
        waitForNetwork: false,
      };
    },
  • Defines the schema for the browser_navigate_back tool, including name, title, description, empty input schema, and readOnly type.
    capability: 'history',
    schema: {
      name: 'browser_navigate_back',
      title: 'Go back',
      description: 'Go back to the previous page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • Exports the browser_navigate_back tool (via goBack factory) as part of the navigate tools module.
    export default (captureSnapshot: boolean) => [
      navigate(captureSnapshot),
      goBack(captureSnapshot),
      goForward(captureSnapshot),
    ];
  • src/tools.ts:35-50 (registration)
    Includes the navigate tools (containing browser_navigate_back) in the snapshotTools array.
    export const snapshotTools: Tool<any>[] = [
      ...common(true),
      ...console,
      ...dialogs(true),
      ...files(true),
      ...install,
      ...keyboard(true),
      ...navigate(true),
      ...network,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs(true),
      ...testing,
      ...wait(true),
    ];
  • src/tools.ts:52-66 (registration)
    Includes the navigate tools (containing browser_navigate_back) in the visionTools array.
    export const visionTools: Tool<any>[] = [
      ...common(false),
      ...console,
      ...dialogs(false),
      ...files(false),
      ...install,
      ...keyboard(false),
      ...navigate(false),
      ...network,
      ...pdf,
      ...tabs(false),
      ...testing,
      ...vision,
      ...wait(false),
    ];
Behavior4/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds context about navigating to the 'previous page', which clarifies the tool's effect on browser state beyond what annotations provide, though it doesn't detail potential errors (e.g., no history). 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, clear sentence with no wasted words. It is front-loaded with the core action, making it highly efficient and easy to understand at a glance.

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 rich annotations, the description is complete enough for an agent to use it correctly. It could slightly improve by mentioning it's for browser navigation history, but the sibling context and annotations provide sufficient coverage.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's action without redundant parameter details, earning a high score for not adding unnecessary information.

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 action (go back) and the resource (previous page) with a specific verb. It distinguishes from siblings like 'browser_navigate_forward' by specifying directionality, and from 'browser_navigate' by focusing on navigation history rather than a new URL.

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 when you want to navigate backward in browser history, but does not explicitly state when not to use it or name alternatives. However, the context of sibling tools (e.g., 'browser_navigate_forward') provides clear alternatives, and the description's specificity gives adequate guidance for typical use cases.

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

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