Skip to main content
Glama

browser_forward

browser_forward

Navigate one entry forward in a browser tab's history using its tab ID. Restore a page you navigated back from, with optional session details so the runtime can block tabs owned by other sessions.

Instructions

Go forward one entry in the tab 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": {
      "tab_id": "<tab_id>"
    },
    "name": "browser_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare the key traits (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the bar is lower, but the description adds essentially nothing beyond the verb. It does not say what happens when there is no forward entry (no-op? error?), whether navigation waits for load, or how this interacts with page state — all relevant for an open-world, non-idempotent navigation action.

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 front-loaded sentence with zero filler. There is nothing redundant or misplaced; the only issue is what it omits, not how it is written.

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 three-parameter navigation tool with no output schema, the definition covers the core action and the schema covers the parameters, but the end-of-history edge case and the navigation completion semantics are left unstated. Adequate to invoke, incomplete for predicting the result.

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%, with tab_id and session_id fully documented in the schema, including the session-ownership rule and sticky session_name behavior. The description adds no parameter-level meaning beyond that, so 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?

States a specific verb (go forward) and resource (tab history) with a clear unit of movement: one entry. It is implicitly distinguishable from the browser_back sibling, but the description never names that counterpart, so the differentiation must be inferred from the tool name rather than read in the text.

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?

The phrase 'forward one entry in the tab history' implies usage occurs after a back navigation, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the browser_back alternative. The agent must infer the pairing from sibling names.

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