Skip to main content
Glama

browser_navigate

Navigate to a URL and retrieve the page's ARIA snapshot with reference handles for subsequent element interaction. Supports configurable wait conditions and timeout.

Instructions

Navigate to a URL. Returns the page's ARIA snapshot (with [ref=...] handles).

    wait_until: when to consider navigation done —
        'domcontentloaded' (default, fast: DOM parsed) | 'commit' (fastest: response
        started) | 'load' (waits for ALL resources — slow/unreliable on heavy or proxied
        sites) | 'networkidle'. Prefer the default and then browser_wait_for a specific
        element; only use 'load' for simple static pages.
    timeout_ms: max navigation wait; None = the engine's configured navigation timeout.
    Auto-creates a session if none exists.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
session_idNo
wait_untilNodomcontentloaded
timeout_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses auto-creation of sessions and the return snapshot format. However, it does not mention error handling, redirect behavior, or other side effects like state changes beyond session creation.

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 concise and front-loaded with the core purpose. Each sentence adds value: returns snapshot, wait_until options, timeout, session creation. No redundancies or fluff.

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?

Given the tool's complexity (navigation with various wait strategies) and the presence of an output schema (not shown but referenced), the description covers return value, timing parameters, and session behavior. It could be improved by mentioning common error scenarios or redirect handling.

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 0%, but the description adds meaning to three of four parameters: wait_until (explains options), timeout_ms (relates to navigation timeout), and session_id (notes auto-creation). The url parameter is obvious from context. This compensates well for the lack of schema descriptions.

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 'Navigate to a URL' and specifies the return value (ARIA snapshot). This directly explains the tool's primary function and distinguishes it from sibling navigation tools like browser_navigate_back or browser_reload.

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 provides detailed guidance on the wait_until parameter, explaining different values and their trade-offs (e.g., preferring default over 'load'). It also mentions auto-creation of sessions. However, it lacks explicit instructions on when to use this tool versus alternatives like browser_reload or browser_navigate_back.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Evil-Bane/eyebrowse'

If you have feedback or need assistance with the MCP directory API, please join our Discord server