Skip to main content
Glama

browser_back

Navigate a browser tab backward in its history using the tab ID, restoring the previous page for continued browsing control.

Instructions

Go back in a tab's history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>"
    },
    "name": "browser_back"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.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 behavioral burden, yet it discloses almost nothing: it does not say what happens when there is no earlier history entry (error vs. no-op), whether the page is reloaded or restored from cache, or whether the call blocks until navigation settles. For an unannotated navigation-mutating tool this is a significant gap.

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?

A single front-loaded sentence with zero wasted words and the key scope (in a tab's history) stated immediately. It is terse rather than padded, though the terseness shades into under-specification.

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

Completeness2/5

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

With no annotations, no output schema, and no parameter discussion, the definition leaves an agent guessing about failure modes at the start of history and about what state the browser will be in afterwards. For such a simple tool the missing pieces are few, but they are the ones that matter for correct invocation.

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 description coverage is 100% and both parameters (tabId, browser) are documented in the schema, including provenance ("Tab id from browser_tabs", "Browser id from browser_list"). The description adds no meaning beyond that, so the baseline 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 gives a specific verb-resource pair ("go back" + "a tab's history"), so an agent knows exactly which operation this performs. It is clearly the inverse of browser_forward, though the description itself does not name that sibling or otherwise state the distinction explicitly.

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 browser_forward, browser_navigate, or browser_reload, and no mention of the obvious precondition (a prior entry must exist in the tab's history). The agent must infer all of the usage context from the name alone.

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