Skip to main content
Glama

Go to a URL

navigate_to_url
Destructive

Navigate the connected browser to a URL that the user asked for. Use it only for websites and accounts that the user owns or is authorized to use, and follow their terms. Stop at logins, MFA and CAPTCHAs and hand control to the user; this tool does not solve CAPTCHAs.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL to navigate to
sessionIdYesSession ID of the connected browser
waitUntilNoWhen to consider navigation completeload
browserAddressNoOptional websocket address for automatic reconnect if session state was lost

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / autoSolveCaptcha
      Removed value: -{
      -  "default": false,
      -  "description": "Automatically solve detected captcha using CloudBrowserPublicApi /solve and inject token",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / autoSubmitCaptcha
      Removed value: -{
      -  "default": false,
      -  "description": "Attempt form submit after injecting solved captcha token",
      -  "type": "boolean"
      -}
    • removedInput schema / properties / captchaExtraData
      Removed value: -{
      -  "additionalProperties": true,
      -  "description": "Additional data forwarded to CloudBrowserPublicApi /solve",
      -  "type": "object"
      -}
    • removedInput schema / properties / captchaType
      Removed value: -{
      -  "description": "Preferred captcha type to solve if multiple are detected",
      -  "enum": [
      -    "recaptcha",
      -    "hcaptcha",
      -    "turnstile"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / detectCaptcha
      Removed value: -{
      -  "default": false,
      -  "description": "Detect captcha widgets after navigation",
      -  "type": "boolean"
      -}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and openWorldHint=true, but the description adds genuinely new behavior: it will not solve CAPTCHAs and it halts at authentication challenges rather than proceeding. That is exactly the kind of operational expectation an agent needs. It does not explain the destructive side effect (what happens to the current page/state on navigation), which is a residual gap.

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?

Two sentences, front-loaded with the core action, and every clause carries a constraint or boundary rather than filler. The second sentence is compound (authorization, stop conditions, CAPTCHA limitation), which slightly crowds the safety guidance but does not obscure it.

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

Completeness3/5

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

With four fully documented parameters and a safety-oriented annotation set, the description covers the main behavioral risks. However, it omits the prerequisite that a browser session must already be connected (a real concern given connect_to_browser and open_browser are siblings) and never explains the destructiveHint implication for existing page state. Adequate, but with identifiable holes for an agent choosing among these tools.

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, sessionId, waitUntil, and browserAddress are all documented in the schema itself, including the waitUntil enum. The description only gestures at the url parameter ('a URL that the user asked for') and says nothing about waitUntil or the reconnect purpose of browserAddress. Baseline 3 applies when the schema does the heavy lifting.

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?

The description opens with a specific verb plus resource: 'Navigate the connected browser to a URL.' That is unambiguous and clearly distinct from siblings such as click_element or get_page_content. It stops short of naming which sibling would be the right alternative when no browser is connected, which keeps it out of 5 territory.

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?

It gives real boundaries: only sites the user owns or is authorized to use, follow their terms, and stop at logins/MFA/CAPTCHAs handing control back. That is explicit when-to-use and when-to-stop guidance. It does not address prerequisites (a connected browser session) or point at connect_to_browser/open_browser as the path when no session exists.

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