Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_click

Clicks or double-clicks a page element using a snapshot reference or CSS selector to automate browser interactions.

Instructions

Click or double-click an element from the latest snapshot or a CSS selector. 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": {
      "target": "<target>"
    },
    "name": "nex_browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
buttonNo
pageIdNoDefaults to the active page
targetYesSnapshot ref (e12) or unique CSS selector
sessionIdNoDefaults to the active session
doubleClickNo

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?

With no annotations, the description carries the full behavioral burden. It does disclose useful constraints: the target must come from the latest snapshot (implying stale refs fail) and browser permissions must never be bypassed, plus an anti-bypass policy for CAPTCHA. It omits what happens on a failed click, whether it auto-waits or scrolls the element into view, and how it behaves when a selector matches multiple nodes.

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 core action is correctly front-loaded in the first sentence. The remaining three sentences are a CAPTCHA sub-workflow that belongs to the captcha tools rather than a click tool, which dilutes the definition and pushes the actual click behavior out of focus.

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 5-parameter mutation-like interaction with no annotations and no output schema, the description should say what a successful click returns and how failures surface. Instead it spends its budget on CAPTCHA orchestration, leaving the core interaction's outcome and error behavior undocumented.

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 60%, with target, pageId and sessionId already documented in the schema, and the description largely restates the target semantics. It adds meaning only for doubleClick by framing it as the alternative to the click action; button (enum) and doubleClick have no explanatory text in either the schema or the description.

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 first sentence gives a specific verb pair (click/double-click) and a precise resource (an element from the latest snapshot or a CSS selector), which is enough to separate it from a generic mouse action. It does not explicitly contrast with siblings such as nex_browser_mouse_click_xy or nex_browser_hover, so the differentiation is only implied.

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 provides explicit routing for the CAPTCHA case (nex_captcha_product_schema -> nex_captcha_detect -> buy/query -> apply in original page) and notes nex_browser_captcha_prepare is optional. However, it gives no guidance on when to use this tool versus nex_browser_mouse_click_xy, nex_browser_hover, or nex_browser_fill_form, which is the primary ambiguity for a click 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