Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_snapshot

Read-only

Capture an accessibility/ARIA snapshot with short-lived actionable refs so you can inspect page structure and act on elements reliably.

Instructions

Capture an accessibility/ARIA snapshot with short-lived actionable refs. 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_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxesNo
depthNo
pageIdNoDefaults to the active page
targetNoSnapshot ref (e12) or unique CSS selector
sessionIdNoDefaults to the active session

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
    • changedInput schema / properties / target / description
      Previous value: -"Snapshot ref such as e12, aria-ref=e12, or a unique CSS selector"New value: +"Snapshot ref (e12) or unique CSS selector"
  2. Addedv2026.8.14

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds two genuine behavioral facts not in the annotations: the returned refs are short-lived, and browser permissions must never be bypassed. It still says nothing about snapshot scope (page vs. frame), size cost of deep trees, or what the returned accessibility tree looks like.

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 well front-loaded and waste-free, but roughly three-quarters of the text is a CAPTCHA workflow that belongs with the captcha tools rather than the snapshot tool. The sentences are individually tight, yet the overall balance is skewed away from the tool's actual function.

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 carries the burden of explaining what a snapshot returns, and it only says 'accessibility/ARIA' plus 'short-lived actionable refs'. For a snapshot/pagination-sensitive tool with five parameters, it should say more about ref lifetime and tree size. The CAPTCHA material it does include is useful but does not fill that gap.

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 60%: pageId, sessionId, and target carry inline descriptions, while boxes and depth are bare. The description only indirectly touches 'target' by calling out refs (e12-style) as the actionable handle, and adds nothing about depth or boxes, so it does not compensate for the undocumented parameters.

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 and resource: 'Capture an accessibility/ARIA snapshot with short-lived actionable refs.' That is enough to distinguish it from sibling tools like nex_browser_get_text or nex_browser_take_screenshot. The remaining four sentences shift to CAPTCHA workflow and do not further sharpen what this tool itself does.

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 present but aimed at a different concern: it tells the agent to start with nex_captcha_product_schema and then nex_captcha_detect when a CAPTCHA is on the page, and that nex_browser_captcha_prepare is optional. Nothing says when to take a snapshot versus nex_browser_get_text, nex_browser_take_screenshot, or nex_browser_evaluate, so the selection guidance for this tool is only implied by 'actionable refs'.

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