Skip to main content
Glama

browser_navigate

Navigates a specified tab to an HTTP or HTTPS URL and waits for page load, letting AI agents move to a page before reading content or filling forms.

Instructions

Navigate a tab to an HTTP or HTTPS URL; wait for document load.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one key trait: the call blocks until document load. It says nothing about timeout behavior, what happens on navigation failure or redirects, whether tab state is destroyed, or what is returned — meaningful gaps for a no-annotation mutation-of-state tool.

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?

A single front-loaded sentence with the action, target, and blocking behavior in order of importance; no filler or restated title.

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?

Without annotations or an output schema, the description should say more about return state and error/timeout handling for a three-parameter navigation tool. The core contract is present but the surrounding behavior an agent needs on failure 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 coverage is 67%, with tabId and browser already documented in the schema. The description adds a real constraint on url (HTTP or HTTPS only) that the schema's bare format:uri does not convey, but it adds nothing for the undocumented aspects of url or the browser parameter.

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 uses a specific verb and resource ("Navigate a tab to an HTTP or HTTPS URL") and pairs it with a load-wait semantic. This lets an agent separate it from browser_open (opening a browser/tab) and browser_back/forward/reload, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

Phrasing "a tab" implies it operates on an existing tab (tabId required) rather than creating one, which implicitly distinguishes it from browser_open. However, there is no explicit when-to-use/when-not statement, no mention of alternatives for opening a new tab, and no guidance on failure or non-HTTP schemes beyond the URL constraint.

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