Skip to main content
Glama

web_back

Navigate back one page in a browser tab's history, mirroring the browser Back button for AI agents controlling Chrome.

Instructions

Go back one entry in the tab's history (like the browser's Back button).

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

Input Schema

NameRequiredDescriptionDefault
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden and does disclose the core behavior: it mutates the tab's history position by one entry. It does not say what happens when there is no prior history (error vs. no-op), whether it requires a page to be loaded, or what the call returns.

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?

A single short sentence, front-loaded with the verb and scope, with the analogy doing useful explanatory work rather than padding. Nothing can be removed without losing information.

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?

For a simple one-optional-parameter tool with no output schema and no annotations, the definition covers what the tool does well enough to invoke it correctly. The only material gap is edge-case behavior when there is no history to go back to.

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 there is a single optional parameter, so the schema already explains target_id and the omit-to-use-active-tab default. The description adds no additional meaning about the parameter, which is the baseline expectation here.

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 names a specific action (go back one entry in the tab's history) with a precise scope ('one entry') and a browser Back-button analogy that makes the effect unambiguous. An agent can distinguish it from sibling navigation tools such as web_forward or web_navigate without opening a schema.

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 browser Back-button analogy gives clear implied context for when to use it, and the 'one entry' phrasing tells the agent this is a single-step history move rather than a fresh navigation. It stops short of naming an explicit alternative (e.g. web_forward) or stating when not to use it.

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