chatgpt-remote-browser-mcp

Navigate shared browser tab

navigate

Navigate the shared browser tab to a specified HTTP(S) URL, updating the page and external site state.

Instructions

Navigate a currently shared tab to an HTTP(S) URL. This changes browser and external-site state.

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": {
      "handle": "<handle>",
      "url": "<url>"
    },
    "name": "navigate"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`handle`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Sep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

The description explicitly notes that navigating changes browser and external-site state, which adds meaningful context beyond the annotations that only mark the tool as non-read-only and open-world. This transparency helps agents anticipate side effects.

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?

The description is two sentences, direct, and free of unnecessary detail. It front-loads the core action and follows with the key side-effect statement.

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 navigation action, the description is mostly complete: it states the target, the required URL scheme, and the side effect. It could mention that the handle must come from a prior shared-tab listing, but this is reasonably inferable from the tool name and sibling list.

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 description maps the URL parameter to an HTTP(S) destination and implies the handle identifies the shared tab, but it does not fully explain the handle's provenance or constraints. Schema provides formats and patterns, so the marginal semantic addition is moderate.

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 clearly states the tool's action: navigating a currently shared tab to an HTTP(S) URL. It also distinguishes this from sibling tools like snapshot or click by specifying the target is a shared tab and the destination is a URL.

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 description implies usage on an already-shared tab, but it does not explicitly contrast with alternatives such as native_browser for opening new tabs or list_shared_tabs for identifying valid handles. The guidance is implied rather than explicit.

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

Deploy Server