Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada

Drag Pointer Between Coordinates

page_pointer_drag
Destructive

Drag from start to end coordinates in a viewport, optionally through ordered waypoints, while holding the mouse button and always releasing it safely.

Instructions

Perform one failure-safe viewport drag through optional ordered waypoints using direct or bounded natural movement while the button remains pressed. Always releases the button.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_xYesViewport drag end X in CSS pixels
end_yYesViewport drag end Y in CSS pixels
buttonNoMouse button held during the dragleft
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.
elementNoHuman-readable draggable element or interaction description
profileNoMovement profile for the approach and every held segment: direct or deterministic bounded natural motiondirect
start_xYesViewport drag start X in CSS pixels
start_yYesViewport drag start Y in CSS pixels
waypointsNoOptional ordered viewport points visited while the button remains pressed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.8
    • addedInput schema / properties / tab_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 128,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Optional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.",
      +  "title": "Tab Id"
      +}
    • changedOutput schema / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "data": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "element": {
      -            "title": "Element",
      -            "type": "string"
      -          },
      -          "end_x": {
      -            "title": "End X",
      -            "type": "number"
      -          },
      -          "end_y": {
      -            "title": "End Y",
      -            "type": "number"
      -          },
      -          "motion": {
      -            "$ref": "#/$defs/PointerDragData"
      -          },
      -          "start_x": {
      -            "title": "Start X",
      -            "type": "number"
      -          },
      -          "start_y": {
      -            "title": "Start Y",
      -            "type": "number"
      -          },
      -          "url": {
      -            "title": "Url",
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "start_x",
      -          "start_y",
      -          "end_x",
      -          "end_y",
      -          "element",
      -          "url",
      -          "motion"
      -        ],
      -        "title": "PagePointerDragData",
      -        "type": "object"
      -      },
      -      "message": {
      -        "type": "string"
      -      },
      -      "ok": {
      -        "const": true
      -      }
      -    },
      -    "required": [
      -      "ok",
      -      "message",
      -      "data"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "data": {
      -        "additionalProperties": true,
      -        "type": "object"
      -      },
      -      "error": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "code": {
      -            "type": "string"
      -          },
      -          "details": {
      -            "additionalProperties": true,
      -            "type": "object"
      -          },
      -          "message": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "code",
      -          "message"
      -        ],
      -        "type": "object"
      -      },
      -      "message": {
      -        "type": "string"
      -      },
      -      "ok": {
      -        "const": false
      -      }
      -    },
      -    "required": [
      -      "ok",
      -      "message",
      -      "error"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "data": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "element": {
      +            "title": "Element",
      +            "type": "string"
      +          },
      +          "end_x": {
      +            "title": "End X",
      +            "type": "number"
      +          },
      +          "end_y": {
      +            "title": "End Y",
      +            "type": "number"
      +          },
      +          "motion": {
      +            "$ref": "#/$defs/PointerDragData"
      +          },
      +          "start_x": {
      +            "title": "Start X",
      +            "type": "number"
      +          },
      +          "start_y": {
      +            "title": "Start Y",
      +            "type": "number"
      +          },
      +          "tab_id": {
      +            "description": "MCP tab id captured for this operation.",
      +            "maxLength": 128,
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "url": {
      +            "title": "Url",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "start_x",
      +          "start_y",
      +          "end_x",
      +          "end_y",
      +          "element",
      +          "url",
      +          "motion",
      +          "tab_id"
      +        ],
      +        "title": "PagePointerDragData",
      +        "type": "object"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "ok": {
      +        "const": true
      +      }
      +    },
      +    "required": [
      +      "ok",
      +      "message",
      +      "data"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "data": {
      +        "additionalProperties": true,
      +        "type": "object"
      +      },
      +      "error": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "details": {
      +            "additionalProperties": true,
      +            "type": "object"
      +          },
      +          "message": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "code",
      +          "message"
      +        ],
      +        "type": "object"
      +      },
      +      "message": {
      +        "type": "string"
      +      },
      +      "ok": {
      +        "const": false
      +      }
      +    },
      +    "required": [
      +      "ok",
      +      "message",
      +      "error"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Addedv0.8.0
  3. Removedv0.7.2
  4. Addedv0.7.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds genuinely useful behavior beyond them: the drag is 'failure-safe' and 'Always releases the button', which tells the agent the button state will not be left pressed on failure. Movement semantics ('direct or bounded natural') are also disclosed. It does not cover permissions or rate limits, but for a pointer action those are minor.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action and the safety guarantee in a prominent final position. Dense but no filler; each clause carries meaning.

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?

An output schema exists so return values need no explanation, and all nine parameters are documented. Combined with the annotations and the stated button-release guarantee, an agent has what it needs to call this correctly; only the sibling-routing guidance is missing.

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 every parameter carries its own description, so the schema does the heavy lifting. The description adds only light context, confirming that waypoints are ordered/optional and that the profile governs approach and held segments. Baseline 3 is appropriate.

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 verb (drag) and resource (viewport pointer) with the coordinate-based mechanic ('through optional ordered waypoints'), which is enough to distinguish it from page_pointer_drag_element. It does not name that sibling or page_pointer_move, so an agent must infer the coordinate-vs-element distinction from the name alone.

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 explicit when-to-use guidance. With page_pointer_drag_element, page_pointer_move and page_click_xy in the sibling set, the description never says when a raw-coordinate drag is preferred over the element-targeted drag. Usage is only implied by the required start/end coordinates in the schema.

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