Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

go_back

Navigate back in browser history to return to the previous page in a Chromium tab, optionally targeting a specific tab by ID when an AI agent needs to reverse a navigation step.

Instructions

Navigate back in browser 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": "go_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not say which tab is affected when tabId is omitted, whether navigation blocks until the page loads, or what occurs at the start of the history stack — all material for an agent driving a browser.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with zero filler. Its brevity borders on under-specification given the missing behavioral details, but nothing is wasted or buried.

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?

The tool is simple — one optional parameter, no output schema, no nested structures — so a short description is defensible. Still, with no annotations at all, the definition should at least state the default tab behavior and the no-history case to be complete.

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 tabId parameter has 100% schema description coverage, so the baseline is 3. The description adds no extra meaning about how tabId interacts with the default (presumably the current tab), so it neither helps nor hurts.

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?

"Navigate back in browser history" pairs a specific verb (navigate back) with a specific resource (browser history), so an agent immediately knows the action. It does not explicitly distinguish itself from the sibling go_forward, but the directional semantics are unambiguous on their own.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus go_forward, open_url, or reload_tab, and no mention of what happens when there is no prior history entry. The only implied usage is the plain meaning of the name.

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