Skip to main content
Glama
Sign In
qualien-mcp

qualien-mcp

Official
by qualienai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

playwright__browser_drag

Destructive

Drag an element from a source location to a target location on a web page using selectors or element descriptions.

Instructions

Perform drag and drop between two elements

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": "playwright__browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
endTargetYesExact target element reference from the page snapshot, or a unique element selector
endElementNoHuman-readable target element description used to obtain the permission to interact with the element
startTargetYesExact target element reference from the page snapshot, or a unique element selector
startElementNoHuman-readable source element description used to obtain the permission to interact with the element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations mark this as destructiveHint: true and openWorldHint: true, indicating the operation modifies state and relies on external context. The description does not elaborate on these or mention any other behavioral details (e.g., element visibility requirements, coordinate-based vs. element-based drag). It provides marginal added value beyond the annotations.

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?

The description is a single sentence that is direct and to the point. No wasted words, but could potentially include more context without becoming overly long.

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?

Given the complexity of a drag-and-drop operation (interaction with page elements, potential for state changes), and lack of output schema, the description is insufficient. It does not explain how elements are identified (via snapshot references), what happens to intermediate mouse events, or how errors are handled.

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 coverage is 100%, meaning all parameters have descriptions in the schema. The description does not add extra meaning beyond what is already in the schema. 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?

The description clearly states the tool performs a 'drag and drop' action between two elements. The verb 'Perform' and resource 'drag and drop' are specific. It distinguishes from siblings like 'click' and 'hover', but not explicitly against 'browser_drop' which might be related.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, 'browser_drop' is a sibling with potentially overlapping functionality, and there is no mention of prerequisites like needing a page snapshot or permissions.

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