Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_navigate

Navigate a selected browser page and return its refreshed accessibility snapshot, enabling page inspection and automation through the active MCP session.

Instructions

Navigate the selected page and return its refreshed accessibility snapshot. Page CAPTCHA: default to nex_captcha_product_schema, collect real page inputs with permitted tools, then use free nex_captcha_detect with productCode/adapter. Confirm application capability before NexCaptcha buy/query and apply the result in the original page. nex_browser_captcha_prepare is optional; never bypass browser permissions.

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": "nex_browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
pageIdNoDefaults to the active page
sessionIdNoDefaults to the active session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2026.10.24
    • changedInput schema / properties / pageId / description
      Previous value: -"Stable page ID; defaults to the session active page"New value: +"Defaults to the active page"
    • changedInput schema / properties / sessionId / description
      Previous value: -"Optional session ID; defaults to this MCP client active session"New value: +"Defaults to the active session"
  2. Addedv2026.8.14

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that the call returns a refreshed accessibility snapshot and adds the constraint 'never bypass browser permissions,' but it omits navigation semantics an agent needs: whether it waits for load, timeout behavior, and what happens to existing page state or open dialogs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and properly front-loaded. The remaining three sentences are a CAPTCHA runbook that, while not pure waste, is disproportionate for a navigate tool and dilutes focus from the core action.

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 no output schema, the description correctly compensates by naming the return value, and its CAPTCHA routing covers an adjacent need. However, for a no-annotation write-adjacent operation it leaves load/error/permission behavior under-specified.

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

Parameters2/5

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

Schema coverage is 67%, with pageId and sessionId already documented in the schema as defaulting to the active page/session. The description's phrase 'the selected page' merely echoes that and adds nothing about the required url parameter's format, nor how sessionId and pageId interact.

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 opening sentence gives a specific verb (Navigate), a target resource (the selected page), and the return value (refreshed accessibility snapshot). It does not distinguish this from the closely related navigation siblings such as nex_browser_reload, nex_browser_go_forward, or nex_browser_open.

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?

Usage guidance is provided, but almost entirely for a tangential CAPTCHA workflow (default to nex_captcha_product_schema, use nex_captcha_detect, confirm capability before nex_captcha_buy/query, nex_browser_captcha_prepare optional). There is no guidance on when to choose navigate over reload/go_forward/go_back, which is the more relevant selection question for this tool.

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

Deploy Server

Other Tools