Skip to main content
Glama
jumodada

DrissionPage MCP Server

by jumodada
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Click Coordinates

page_click_xy
Destructive

Click precise viewport CSS coordinates with left, right, or middle mouse buttons, using direct or natural pointer movement and optional press delay for browser automation.

Instructions

Move the viewport pointer to exact CSS pixel coordinates using a direct or bounded natural trajectory, optionally wait for an explicit delay, then press and release one mouse button.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesViewport X coordinate in CSS pixels
yYesViewport Y coordinate in CSS pixels
buttonNoMouse button to press and releaseleft
tab_idNoOptional MCP or native DrissionPage tab id. When omitted, the current tab is captured at call start.
elementNoHuman-readable element or interaction description
profileNoMovement profile: direct emits one exact move; natural emits a deterministic 24-step eased cubic Bezier path with bounded 8-14ms intervals and an exact endpointdirect
delay_before_press_msNoOptional delay after pointer arrival and before mousePressed. This is timing control, not target-stability detection; moving targets require a fresh screenshot or selector-first action.

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"
-          },
-          "motion": {
-            "$ref": "#/$defs/PointerMotionData"
-          },
-          "url": {
-            "title": "Url",
-            "type": "string"
-          },
-          "x": {
-            "title": "X",
-            "type": "number"
-          },
-          "y": {
-            "title": "Y",
-            "type": "number"
-          }
-        },
-        "required": [
-          "x",
-          "y",
-          "element",
-          "url",
-          "motion"
-        ],
-        "title": "PageClickXYData",
-        "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"
+          },
+          "motion": {
+            "$ref": "#/$defs/PointerMotionData"
+          },
+          "tab_id": {
+            "description": "MCP tab id captured for this operation.",
+            "maxLength": 128,
+            "minLength": 1,
+            "type": "string"
+          },
+          "url": {
+            "title": "Url",
+            "type": "string"
+          },
+          "x": {
+            "title": "X",
+            "type": "number"
+          },
+          "y": {
+            "title": "Y",
+            "type": "number"
+          }
+        },
+        "required": [
+          "x",
+          "y",
+          "element",
+          "url",
+          "motion",
+          "tab_id"
+        ],
+        "title": "PageClickXYData",
+        "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. Changed2 schema fields changedv0.5.0
    • addedInput schema / additionalProperties
      Added value: +false
    • removedOutput schema / additionalProperties
      Removed value: -false
  5. First observedv0.4.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the two-phase move/click nature and the optional pre-press delay, but repeats trajectory detail that the schema's profile field already documents. It adds only modest value beyond structured fields.

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?

A single front-loaded sentence that describes the full action sequence with no filler. It is dense but appropriately sized for a click primitive.

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?

An output schema exists and annotations carry the safety profile, so the description need not explain returns. Still, for a destructive click tool surrounded by many alternatives, it should at least signal when the coordinate-based route is appropriate; that routing information is absent.

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 every parameter is already documented in the schema, including the direct/natural profile semantics and the delay caveat. The description restates the trajectory and delay concepts without adding syntax or constraints beyond the schema. Baseline 3 applies.

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+resource: move pointer to coordinates, then press and release a button. It is clear what the tool does. However, it never differentiates itself from close siblings like element_click or page_pointer_move, which is important given the crowded click/pointer family.

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?

No when-to-use guidance appears in the description. It does not tell the agent when coordinate-based clicking is preferable to element_click or selector-first actions, even though that is the key routing decision. The only related hint (moving targets need a fresh screenshot) lives in the schema, not the description.

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