Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_get_text

Read-only

Extract visible text from a page or a specific snapshot ref or CSS selector, so agents can read rendered content for inspection, scraping, or verification.

Instructions

Read visible text from the page or one target. 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_get_text"
  }
}

Input Schema

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

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

readOnlyHint=true already declares the safe-read profile, so the description only needs to add context. It does add some: only *visible* text is returned, pageId/sessionId fall back to the active page and session, and browser permissions must never be bypassed. It omits practical behavior an agent would want, such as whether output is truncated, whether it covers cross-frame content, and what happens if a CAPTCHA blocks the read.

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 first sentence is well front-loaded, but roughly three quarters of the text is a CAPTCHA recovery procedure that belongs to the nex_captcha_* and nex_browser_captcha_* tools rather than to a text-read tool. That bulk buries the one thing the agent needs and makes the definition read as two unrelated instructions stapled together.

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

Completeness4/5

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

For a three-optional-parameter read only tool with full schema coverage and a readOnlyHint, the description supplies what is needed to call it correctly: scope, defaults, and the permission constraint. Missing detail about output size limits or frame coverage is a modest gap rather than a blocker, since no output schema exists but the return value is obvious from the name.

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 all three optional parameters are already documented in the schema, which sets the baseline at 3. The phrase "page or one target" adds only marginal meaning beyond the schema's own "Snapshot ref (e12) or unique CSS selector" and "Defaults to the active page".

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?

"Read visible text from the page or one target" gives a specific verb (read) plus resource (visible page text) and a scope choice (whole page vs. a single target), which is enough to distinguish it from the snapshot and evaluate siblings at a glance. It stops short of explicitly contrasting with nex_browser_snapshot or nex_browser_evaluate, which are the closest alternatives.

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

Usage Guidelines2/5

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

The description never says when to choose this over nex_browser_snapshot, nex_browser_evaluate, or page_title. The alternatives it does name (nex_captcha_product_schema, nex_captcha_detect, nex_captcha_buy) are routing instructions for a CAPTCHA encounter, not guidance about when to use text extraction, so the core usage decision is left to inference.

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