Skip to main content
Glama
yinnho

AginxBrowser

by yinnho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

session_drag

Simulate human-like mouse drags between viewport positions to move drag targets, select canvas elements, or solve captcha sliders while avoiding anti-bot detection. Option for exact linear movement.

Instructions

Drag the mouse from one viewport position to another: press at from, steps mousemove events, release at to. The trajectory is humanized by default (eased velocity, wobble, jittered timing, overshoot) — the shapes anti-bot checks score for; pass humanize:false for exact linear interpolation. Moves AMarker-style drag targets, canvas selections and captcha sliders that only track while the pointer travels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesWhere to release it
fromYesWhere to press the mouse button down
stepsNoInterpolated mousemove events between from and to. Default: 24 with humanize on, 10 without
delay_msNoMean delay between moves in ms (default 18 humanized / 30 linear) — per-step timing is jittered around this when humanizing
humanizeNoHumanize the trajectory: minimum-jerk easing, perpendicular wobble, timing jitter, grip/settle pauses, occasional hesitation and overshoot-and-correct. Set false when a test/tool needs exact linear interpolation. Default: true
session_idYesSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.1
    • changedInput schema / properties / delay_ms / description
      Previous value: -"Delay between moves in ms (default 30) — gives mousemove-driven\nwidgets time to react per step"New value: +"Mean delay between moves in ms (default 18 humanized / 30 linear) —\nper-step timing is jittered around this when humanizing"
    • addedInput schema / properties / humanize
      Added value: +{
+  "default": null,
+  "description": "Humanize the trajectory: minimum-jerk easing, perpendicular wobble,\ntiming jitter, grip/settle pauses, occasional hesitation and\novershoot-and-correct. Set false when a test/tool needs exact linear\ninterpolation. Default: true",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • changedInput schema / properties / steps / description
      Previous value: -"Interpolated mousemove events between from and to (default 10)"New value: +"Interpolated mousemove events between from and to. Default: 24 with\nhumanize on, 10 without"
    • removedInput schema / title
      Removed value: -"SessionDragParams"
  2. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations are minimal (only a title), so the description carries the full burden. It discloses the humanized trajectory behavior (eased velocity, wobble, jittered timing, overshoot) and explains that it exists to pass anti-bot checks. It also clarifies the behavior of the `humanize` flag. This is substantial behavioral context beyond what the schema provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with zero filler. The first sentence front-loads the core action and mechanics; the second adds crucial behavioral nuance (humanization) and use-case examples. Every word earns its place.

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 complex action with six parameters, the description covers the purpose, the humanization behavior, and typical use cases. It does not explicitly mention the session context, but the `session_id` parameter and tool name make that clear. The lack of an output schema is acceptable since the action is a gesture with no meaningful return value. The description is sufficiently complete for an agent to call it 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%, so all six parameters are already documented in the schema. The description adds some contextual meaning (e.g., that `steps` and `humanize` relate to trajectory smoothing), but it does not significantly enhance parameter understanding beyond what the schema provides. Baseline 3 is appropriate given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Drag'), a specific resource ('the mouse'), and precise mechanics (press at `from`, mousemove events, release at `to`). It also names concrete target types (AMarker-style drag targets, canvas selections, captcha sliders), which clearly distinguishes it from sibling click tools like session_click and session_click_xy.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool—when dragging is needed—and even gives examples of drag targets that only track while the pointer travels. However, it does not explicitly mention when NOT to use it or point to alternative tools (e.g., using session_click for simple clicks). Since the sibling list includes click tools, this guidance is implied but not explicit.

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