Skip to main content
Glama

Browser Navigate Url

browser_navigate_url
Destructive

Use this to navigate an identified Chromium tab to a user-requested URL via the paired computer local CDP session. Inspect or choose the target tab first; navigation may discard unsaved page 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": {
      "device": "<device>",
      "url": "<url>"
    },
    "name": "browser_navigate_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesDestination URL for action=url or action=new_tab.
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/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is known; the description still earns credit by naming the concrete consequence ('navigation may discard unsaved page state') and the transport dependency (paired computer local CDP session). It does not discuss timeouts or failure behavior, which is a modest gap.

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?

Two sentences with zero padding; the action and its scope come first, followed by the prerequisite and the risk warning. Every clause carries information an agent needs before invoking.

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 full parameter descriptions, the description only needs to cover intent, prerequisite, and risk, and it does all three. Minor absences, such as whether navigation waits on the load event or how failures surface, are already covered by schema fields like wait and timeout_ms.

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 coverage is 100%, so all eight parameters including device, target_id, title, url_contains, and wait are already documented in structured form. The description only implies that tab selection is possible ('identified ... tab') without adding syntax or precedence rules for target_id versus title versus url_contains, 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 and resource ('navigate an identified Chromium tab to a user-requested URL') and scopes it to an existing tab in a paired computer's CDP session, which separates it from tab-creation and reload siblings. It does not explicitly name browser_new_tab or browser_reload as the alternatives, so the differentiation is implied rather than stated.

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?

'Inspect or choose the target tab first' gives a concrete prerequisite that points the agent at browser_tabs before calling. It stops short of explicitly excluding alternatives such as browser_new_tab or browser_reload, so the when-not guidance is only implicit.

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