Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_mouse_click_xy

Clicks at specified x/y viewport CSS-pixel coordinates, including canvas, iframes, and injected overlays, for precise page interactions when element selectors are unavailable.

Instructions

Click at x/y in viewport CSS pixels, including canvas, iframes and extension overlays injected into the page (not native toolbar popups). Take coordinates from a fresh screenshot: divide image pixels by pixelsPerCssPixel, then add the returned origin. 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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "nex_browser_mouse_click_xy"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
delayNo
buttonNo
pageIdNoDefaults to the active page
sessionIdNoDefaults to the active session
clickCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2026.10.24

TDQS

B3.3/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 behavioral burden; it does disclose DOM reach into iframes/extension overlays and the native-toolbar-popup exclusion, which is useful beyond a bare verb. It does not state failure behavior for out-of-viewport coordinates, whether the target must be scrolled into view, focus requirement, or what a call returns, and 'never bypass browser permissions' is a caveat without an actionable prerequisite.

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?

Front-loaded correctly: the first two sentences cover what is clicked and how to compute coordinates, and those earn their place. The three following sentences are a CAPTCHA playbook naming several other tools; it is workflow context, but it dominates a definition for a low-level mouse click and dilutes 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?

No annotations and no output schema, so the description must hold everything; it covers spatial semantics well but omits return values, error/edge behavior, and most parameter meaning for a 7-parameter tool. Adequate to attempt a call with coordinates in hand, but not sufficient for confident use across pageId/sessionId or clickCount scenarios.

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 only 29% across 7 parameters, so the description should compensate more than it does. It adds real meaning for x/y (viewport CSS pixels and the screenshot-to-coordinate conversion), but delay, button, clickCount, pageId, and sessionId go unexplained beyond the two short schema descriptions.

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?

States a specific action (click) and precise resource (x/y viewport CSS pixels) and clarifies scope by naming what it reaches: canvas, iframes, and extension overlays, but not native toolbar popups. It never explicitly contrasts with the sibling nex_browser_click (element/selector-based clicking), so the agent must infer which click tool to pick.

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?

Gives concrete usage direction for deriving coordinates from a fresh screenshot (divide by pixelsPerCssPixel, add returned origin), which is genuinely actionable. However, it offers no when-not-to-use guidance versus nex_browser_click or drag/hover, and the remaining guidance is CAPTCHA workflow routing rather than selection criteria 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