Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_reload

Reload a browser page by page or session ID to refresh its content; confirm with the user before reloading a form with entered data.

Instructions

Reload the page. Ask the user before reloading a filled form. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nex_browser_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose one important behavioral trait — reloading can destroy unsaved form state — plus a permissions caveat, which is real value. It omits whether the call waits for the load to finish, whether session/page context survives, and what the call returns.

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

Conciseness2/5

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

The action statement is correctly front-loaded in the first sentence, but the remaining ~70% of the text is a multi-step CAPTCHA policy that is boilerplate relative to a simple reload call. Most sentences do not earn their place for this specific tool.

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?

For a two-optional-parameter tool with no output schema and no annotations, the definition covers the key danger (filled forms) and a permissions constraint. It is missing return-value behavior and load-wait semantics, and it spends its remaining budget on off-topic CAPTCHA orchestration rather than completing the picture for reload.

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 100%: both pageId and sessionId are documented with their defaults (active page / active session). The description adds no further meaning about these parameters, so the baseline of 3 applies since the schema does all the work.

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?

"Reload the page" is a specific verb+resource that an agent can map to the reload action, and it is distinguishable from nearby siblings like go_back, go_forward, and navigate. It stops short of explicitly stating how it differs from those siblings, but the core action is unambiguous.

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?

It gives one concrete when-to-use rule (ask the user before reloading a filled form), which is genuinely useful. However, there is no guidance on reload vs. navigate/go_back, and the bulk of the remaining text is a generic CAPTCHA escalation workflow that is conditional and largely tangential to the reload action itself.

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