Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Go Back

go_back

Navigate to the previous page in browser history to review or interact with earlier content. Returns a snapshot of the resulting page with interactive elements.

Instructions

Go back one page in browser history. Returns a fresh page snapshot of the resulting page with its interactive elements.

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": "go_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idNoPage ID. If omitted, operates on the most recently used page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page_id / description
      Added value: +"Page ID. If omitted, operates on the most recently used page."
  2. First observedv4.6.4

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided. Description discloses return value (fresh snapshot with interactive elements) but omits edge cases like history boundary or performance impact.

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?

Single sentence with clear action and result. No waste. Front-loaded with the core action.

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

Completeness5/5

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

Given the simplicity (1 optional param, no output schema), the description fully covers what the tool does and returns. No gaps.

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?

Schema coverage is 100% and the parameter description is complete. The tool description adds no extra meaning beyond the schema, so baseline score applies.

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?

Clearly states verb ('Go back') and resource ('browser history'), and distinguishes from sibling 'go_forward' by specifying direction. No ambiguity.

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?

Implies use for navigating backward, but does not explicitly state when to avoid it (e.g., at history start) or compare with alternatives like 'navigate'.

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

Deploy Server

Other Tools