Skip to main content
Glama

navigate_back

Go back to the previous page in the browser session history, enabling you to return to prior states during site inspection and responsive testing.

Instructions

Navigate back to the previous page in the browser session history.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "navigate_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNoTimeout in ms (default: 15000ms).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, yet it only restates the navigation action. It does not say what happens at the start of history, whether the call waits for the page to load, or whether it returns the resulting page state — all relevant for an agent sequencing browser actions.

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?

One short sentence, front-loaded with the action and scoped by the qualifying phrase. There is no filler and nothing that could be trimmed.

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?

For a one-parameter, non-destructive navigation tool the description is close to adequate, and the schema covers the only parameter. It is still thin on edge-case behavior (empty history, load waiting) that an agent driving a browser session would benefit from knowing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional timeout parameter is fully documented in the schema ('Timeout in ms (default: 15000ms)'), and the description adds nothing about it. With 100% schema description coverage, the baseline of 3 applies.

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 states a specific verb and resource ('Navigate back') scoped to 'the browser session history', which is concrete enough for an agent to act on. It is not explicitly differentiated from navigate_forward or reload_page, but the direction and history semantics are unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: 'previous page in the browser session history' tells the agent the precondition, but there is no statement of when to prefer this over reload_page, open_page, or navigate_forward, and no note about what to do if there is no prior entry.

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