Skip to main content
Glama

Navigate to a URL

browser_navigate

Open a URL, wait for load, and return a compact Semantic Markdown snapshot with stable element references for inspecting content and acting on page elements; ads and heavy media are blocked.

Instructions

Open a URL in the browser, wait for the page to settle, then return a compact Semantic Markdown snapshot. Interactive elements are listed with stable [eN] references (e.g. "[e12] Search (button)"). Use those references with browser_batch to act on the page. Ads, trackers and heavy media are blocked by default.

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

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL to open (a bare domain is prefixed with https://)
scopeNoOnly include page content matching these terms (for example a product name).
timeoutNoNavigation timeout in ms. Default: 45000
waitUntilNoNavigation wait condition. Default: domcontentloaded

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses the wait-for-settle behavior, the return format, the stable reference scheme, and that ads, trackers and heavy media are blocked by default. It omits session/auth state, whether the page persists for later browser_batch calls, and timeout/failure behavior.

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?

Three tight sentences, front-loaded with the action and result, followed by the follow-up tool and the blocking policy. No filler and nothing redundant with the schema.

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 no output schema and no annotations, the description still explains the returned snapshot format and reference scheme, which is the critical part. Gaps remain around page lifecycle and error handling, but the essentials for invoking it correctly are present.

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 the baseline is 3. The description adds no detail on scope filtering, the timeout value, or how waitUntil interacts with the "wait for the page to settle" claim, so it does not exceed the 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?

States a concrete verb and resource ("Open a URL in the browser") plus the exact artifact returned ("compact Semantic Markdown snapshot" with [eN] references). It also distinguishes itself from browser_batch by scoping that tool to acting on the listed references.

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?

The description makes the workflow explicit: navigate first, then use the [eN] references with browser_batch to act. It gives clear context for use but never states when not to use it, e.g. versus browser_snapshot for re-reading an already-open page.

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