Skip to main content
Glama

Browser Forward

browser_forward
Destructive

Use this to move forward one step in the history of a selected Chromium tab. It requires previous backward navigation and may discard unsaved page state, even though it does not submit forms.

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": {
      "device": "<device>"
    },
    "name": "browser_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait for the page load event; default true.
titleNoChoose a page whose title contains this text.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
endpointNoLoopback Chrome DevTools endpoint. Defaults to REMCP_CDP_URL or http://127.0.0.1:9222.
target_idNoPage target id returned by browser_tabs.
timeout_msNoTimeout in milliseconds.
url_containsNoChoose a page whose URL contains this text.

Output Schema

NameRequiredDescriptionDefault
dataNoBrowser navigate structured result for browser_navigate. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the concrete consequence — 'may discard unsaved page state' — and clarifies the safety boundary with 'does not submit forms.' That is genuine value beyond the structured fields, though it says nothing about how the selected tab is targeted when several match.

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?

Two sentences, front-loaded with the action and followed by the prerequisite and side effect. The trailing clause 'even though it does not submit forms' is slightly awkward and reads as a defensive clarification rather than essential guidance, but nothing is wasted overall.

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?

With an output schema present and annotations covering safety signals, the description only needs to convey the prerequisite and the destructive side effect, and it does both. The one remaining gap is tab-selection behavior when multiple tabs match the title/URL filters, which is left entirely to the schema.

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%, so device, target_id, title, url_contains, wait, and timeout_ms are all already documented in the schema. The description adds no additional parameter guidance, which matches the baseline for a fully documented schema.

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 verb and resource — 'move forward one step in the history of a selected Chromium tab' — which unambiguously separates it from browser_back, browser_navigate_url, and browser_reload. An agent can select it without reading the 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?

It states a real prerequisite: 'It requires previous backward navigation,' which tells the agent when the tool will not apply. It does not explicitly name browser_back as the required predecessor or say what to do if there is no forward history, leaving a small inference gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources