Skip to main content
Glama

Navigate to a URL

browser_navigate

Use for: loading a web page in a real Chromium browser and reading it. Returns the page title, final URL and a clean text extract (up to 8000 chars). Don't use when: you only need raw HTML or an API response — a plain HTTP fetch is cheaper. Errors are structured: NAV_TIMEOUT, NAV_FAILED, INVALID_URL. Paid: $0.005 per call via x402 (Base USDC, Solana USDC, or XRPL XRP).

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": {
      "session_id": "<session_id>",
      "url": "<url>"
    },
    "name": "browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL to load.
wait_forNoOptional CSS selector to wait for after load (max 10s).
session_idYesSession ID. Reuse the same ID to keep cookies, login state and page position across calls; a new ID starts a fresh browser.

Output Schema

NameRequiredDescriptionDefault
urlYes
textYes
titleYes
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, openWorldHint=true) by disclosing cost ($0.005/call via x402), the 8000-char extraction cap, the 10s wait_for ceiling, and the exact structured error codes (NAV_TIMEOUT, NAV_FAILED, INVALID_URL). Cost and failure modes are the two things an agent most needs and neither is expressible in the schema.

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?

Four short sentences in a clear Use-for / Don't-use / Returns / Errors / Cost order. The decision-relevant guidance (when to use, when not to) is front-loaded and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be spelled out, yet the description still summarizes the return and adds error taxonomy and pricing that the schema cannot express. Nothing an agent needs to decide or invoke correctly is missing.

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 url, wait_for and session_id are already fully documented in structured form, including the session-reuse semantics. The description adds no parameter-level detail beyond what the schema carries, so baseline 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 ('loading a web page in a real Chromium browser and reading it') and names exactly what comes back (title, final URL, text extract). It implicitly separates itself from browser_snapshot/browser_screenshot by emphasizing the text extract, though it never names those sibling tools directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use for' and 'Don't use when' sections give both the selection condition and the exclusion, with the cheaper alternative (plain HTTP fetch) named and the reason given. This is exactly the routing guidance an agent needs before touching a paid call.

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