Skip to main content
Glama
NexBrowser MCP Server

NexBrowser MCP Server

Official
by nex-browser

nex_browser_drag

Drag one snapshot ref or unique CSS selector to another on the active page to perform drag-and-drop actions during browser automation.

Instructions

Drag one snapshot ref or selector to another. 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": {
      "startTarget": "<startTarget>",
      "endTarget": "<endTarget>"
    },
    "name": "nex_browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdNoDefaults to the active page
endTargetYesSnapshot ref (e12) or unique CSS selector
sessionIdNoDefaults to the active session
startTargetYesSnapshot ref (e12) or unique CSS selector

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2026.10.24
    • changedInput schema / properties / endTarget / 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"
    • 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 / startTarget / 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

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what a drag does – whether it emits HTML5 drag events, how many intermediate mouse moves occur, whether it scrolls targets into view, what happens when a selector is missing, or whether the action waits for the page. The CAPTCHA text adds no behavioral context about dragging itself.

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 relevant content is a single front-loaded sentence; the rest is a multi-sentence CAPTCHA procedure about product schemas, adapters, and purchasing that does not belong on a drag tool and buries the payload. It reads as boilerplate copied across tools rather than tool-specific guidance.

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

Completeness2/5

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

With no annotations, no output schema, and a mutation-style interaction, the description should explain drag semantics, failure modes, and any capability restrictions. Instead it leaves all of that unstated and spends its length on an unrelated CAPTCHA flow, so an agent still lacks what it needs to invoke drag correctly.

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%, and the schema already documents startTarget/endTarget as 'Snapshot ref (e12) or unique CSS selector', so the description's mention of refs and selectors is redundant. pageId and sessionId defaults are explained only in the schema. Baseline 3 applies because the schema does the heavy lifting.

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 'Drag one snapshot ref or selector to another' is a precise verb+resource statement that separates it from siblings like nex_browser_hover and nex_browser_mouse_click_xy. However, the majority of the remaining text describes an unrelated CAPTCHA workflow, which dilutes rather than reinforces the stated purpose.

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?

There is no guidance on when to drag rather than click, hover, or use mouse_click_xy, nor on prerequisites such as the element being visible or the snapshot being fresh. The CAPTCHA paragraph does provide when-to-use guidance, but for a different workflow (nex_captcha_detect, nex_captcha_buy) rather than for this drag 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