PhantomHand

Overview Schema Source Related Servers Discussions Admin

browser_drag

Drag from one coordinate to another with intermediate steps for drag-and-drop, slider manipulation, or text selection.

Instructions

Drag from one coordinate to another with smooth intermediate steps. Useful for drag-and-drop, slider manipulation, or text selection by dragging.

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": {
      "fromX": "<fromX>",
      "fromY": "<fromY>",
      "toX": "<toX>",
      "toY": "<toY>"
    },
    "name": "browser_drag"
  }
}

Input Schema

Name	Required	Description
`toX`	Yes
`toY`	Yes
`fromX`	Yes
`fromY`	Yes
`steps`	No	Number of intermediate mouse-move steps (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Mentions 'smooth intermediate steps' and default steps count, but lacks details on coordinate system, mouse button release, or prerequisites. No annotations provided, so description carries burden but insufficiently covers behavioral aspects.

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?

Two concise, front-loaded sentences with action verb and examples. No wasted words.

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?

Covers purpose and use cases, but lacks details on coordinate system, prerequisites (element visibility), drop behavior, and error handling. No output schema exists, so more behavioral context would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only the 'steps' parameter is described in schema (20% coverage). The description does not clarify what coordinates (fromX, fromY, toX, toY) represent relative to (e.g., viewport, element). Description fails to compensate for low schema 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?

Clearly states 'Drag from one coordinate to another' and lists use cases (drag-and-drop, slider, text selection). Distinct from siblings like browser_click and browser_scroll.

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?

Lists specific use cases (drag-and-drop, slider manipulation, text selection) but does not explicitly compare to alternatives or state when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.