Skip to main content
Glama

browser_navigate_back

Read-only

Navigate back to the previous web page in the browser history using the Playwright MCP server's structured accessibility snapshots.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the goBack action on the browser tab's page, includes a snapshot in the response, and appends the equivalent Playwright code.
    handle: async (tab, params, response) => {
      await tab.page.goBack();
      response.setIncludeSnapshot();
      response.addCode(`await page.goBack();`);
    },
  • Schema defining the tool's name, title, description, empty input schema (no parameters), and readOnly type.
    schema: {
      name: 'browser_navigate_back',
      title: 'Go back',
      description: 'Go back to the previous page',
      inputSchema: z.object({}),
      type: 'readOnly',
    },
  • src/tools.ts:36-52 (registration)
    Global registration of all tools, including browser_navigate_back via spread of imported navigate tools array.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
  • Local export of the tool (goBack) as part of the navigate tools array for higher-level registration.
    export default [
      navigate,
      goBack,
      goForward,
    ];
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, covering safety and scope. The description adds behavioral context by specifying 'previous page', which implies reliance on browser history state—a useful detail beyond annotations. 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, efficient sentence with zero waste. It's front-loaded with the core action and appropriately sized for a simple tool with no parameters.

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 basic use. However, it could mention potential limitations (e.g., no history available) or return values, though not strictly required.

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 description coverage, the baseline is 4. The description doesn't need to explain parameters, and it appropriately omits any parameter details, focusing solely on the tool's action.

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 target (previous page) with a specific verb+resource. It distinguishes from siblings like 'browser_navigate_forward' by specifying directionality, making the purpose 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 context (navigation history) but doesn't explicitly state when to use this vs. alternatives like 'browser_navigate' or 'browser_navigate_forward'. It provides clear context for browser navigation but lacks explicit exclusions or named alternatives.

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

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