Skip to main content
Glama

Open a URL

browser_navigate
Destructive

Opens an http(s) URL in the current tab and returns a visible-page snapshot with element refs and counts, enabling web navigation and page inspection.

Instructions

Open an http(s) URL in the current tab. Returns evidence and a snapshot of the visible screen (elements carry refs like e12), with counts of what is above and below. Words like cheapest, latest, highest-rated or most mean the site's own sort or tab for that order (a list's default order is usually something else, e.g. 'Best' or 'Featured'): apply it, then read the top. Over several sites, finish one and note the values the next needs before opening it. A task that names no site: search the web first with your own search tool to pick the site, or answer from the search when that is enough; open a site when the task needs one (a price for dates, a form, an account).

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 http(s) URL
snapshotNoDefault true. false: no page snapshot, only what happened (title, counts). Only when this same reply also reads the page with browser_query and you will not act on it; keep it for a page you have not seen or whose tabs, sorts, filters or forms you may use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations it discloses the return shape (evidence, visible-screen snapshot, element refs like e12, counts above and below) and describes how the site's own sort/tab semantics should be interpreted. What is missing is the destructive consequence flagged by destructiveHint=true: navigating 'in the current tab' replaces the existing page, and the description never warns that in-page state or unsaved form input is lost.

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?

The action and return format are front-loaded in the first sentence, and the remaining sentences pack distinct, useful rules rather than repetition. It is dense but long for a single tool, and the ranking-word guidance ('cheapest, latest, highest-rated') is a fairly specialized aside that lengthens the core navigation instruction.

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, the description carries the burden of explaining return values and does so at a useful level of detail, plus multi-site sequencing and no-site fallback. It stops short of covering failure behavior (unreachable URL, timeouts, redirects) and pagination, which matter for an open-world navigation tool with destructive navigation semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning to the snapshot flag by explaining that a snapshot contains element refs and above/below counts, and by implying it is needed for pages whose tabs, sorts, filters or forms you may use. The url parameter adds nothing beyond the schema, which is acceptable since the schema already specifies format and absoluteness.

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 definition states a specific verb and resource with scope: 'Open an http(s) URL in the current tab'. 'Current tab' implicitly distinguishes it from tab-creating siblings such as browser_tabs, and the second clause clarifies what the call produces. An agent can identify the operation without opening 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 Guidelines5/5

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

It gives explicit routing rules: search the web first with your own search tool when no site is named, open a site only when the task needs one (price for dates, a form, an account), and sequence multi-site work by finishing one site before opening the next. It also constrains snapshot=false to the narrow case where this reply also reads the page with browser_query and will not act on it.

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