Skip to main content
Glama
lewisvoncken

Playwright MCP

by lewisvoncken

browser_drag

Destructive

Drag elements between two specified locations on web pages for browser automation testing and interaction.

Instructions

Perform drag and drop between two elements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startElementYesHuman-readable source element description used to obtain the permission to interact with the element
startRefYesExact source element reference from the page snapshot
endElementYesHuman-readable target element description used to obtain the permission to interact with the element
endRefYesExact target element reference from the page snapshot

Implementation Reference

  • The handle function executes the drag and drop operation by resolving locators from the page snapshot and performing dragTo action on them, while also generating equivalent Playwright code.
    handle: async (context, params) => {
      const snapshot = context.currentTabOrDie().snapshotOrDie();
      const startLocator = snapshot.refLocator({ ref: params.startRef, element: params.startElement });
      const endLocator = snapshot.refLocator({ ref: params.endRef, element: params.endElement });
    
      const code = [
        `// Drag ${params.startElement} to ${params.endElement}`,
        `await page.${await generateLocator(startLocator)}.dragTo(page.${await generateLocator(endLocator)});`
      ];
    
      return {
        code,
        action: () => startLocator.dragTo(endLocator),
        captureSnapshot: true,
        waitForNetwork: true,
      };
    },
  • Zod schema defining the input for the browser_drag tool, requiring start/end element descriptions and refs.
    schema: {
      name: 'browser_drag',
      title: 'Drag mouse',
      description: 'Perform drag and drop between two elements',
      inputSchema: z.object({
        startElement: z.string().describe('Human-readable source element description used to obtain the permission to interact with the element'),
        startRef: z.string().describe('Exact source element reference from the page snapshot'),
        endElement: z.string().describe('Human-readable target element description used to obtain the permission to interact with the element'),
        endRef: z.string().describe('Exact target element reference from the page snapshot'),
      }),
      type: 'destructive',
    },
  • The defineTool call that defines and registers the browser_drag tool, including its schema and handler.
    const drag = defineTool({
      capability: 'core',
      schema: {
        name: 'browser_drag',
        title: 'Drag mouse',
        description: 'Perform drag and drop between two elements',
        inputSchema: z.object({
          startElement: z.string().describe('Human-readable source element description used to obtain the permission to interact with the element'),
          startRef: z.string().describe('Exact source element reference from the page snapshot'),
          endElement: z.string().describe('Human-readable target element description used to obtain the permission to interact with the element'),
          endRef: z.string().describe('Exact target element reference from the page snapshot'),
        }),
        type: 'destructive',
      },
    
      handle: async (context, params) => {
        const snapshot = context.currentTabOrDie().snapshotOrDie();
        const startLocator = snapshot.refLocator({ ref: params.startRef, element: params.startElement });
        const endLocator = snapshot.refLocator({ ref: params.endRef, element: params.endElement });
    
        const code = [
          `// Drag ${params.startElement} to ${params.endElement}`,
          `await page.${await generateLocator(startLocator)}.dragTo(page.${await generateLocator(endLocator)});`
        ];
    
        return {
          code,
          action: () => startLocator.dragTo(endLocator),
          captureSnapshot: true,
          waitForNetwork: true,
        };
      },
    });
  • Module exports an array of tools including the drag tool for overall registration.
    export default [
      snapshot,
      click,
      drag,
      hover,
      type,
      selectOption,
    ];
Behavior3/5

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

Annotations already indicate this is a destructive (destructiveHint: true), non-read-only (readOnlyHint: false) operation with open-world implications (openWorldHint: true). The description adds minimal behavioral context beyond this, as it doesn't explain what 'destructive' entails (e.g., UI state changes, data modifications) or any side effects like page reloads. No contradiction with annotations exists.

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 a single, front-loaded sentence that directly states the tool's function without unnecessary words. Every part of the sentence ('Perform drag and drop between two elements') is essential, making it highly efficient and well-structured.

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?

Given the tool's complexity (interactive, destructive action with 4 required parameters) and lack of output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral outcomes, error conditions, or integration with sibling tools like browser_snapshot for obtaining element references, leaving gaps in context.

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%, with clear documentation for all four parameters (startElement, startRef, endElement, endRef). The description adds no additional meaning about parameters beyond implying they specify source and target elements, so it meets the baseline of 3 without compensating for gaps.

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 action ('Perform drag and drop') and the target ('between two elements'), which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like browser_click or browser_hover, which are also interaction tools but for different actions.

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. It doesn't mention prerequisites (e.g., needing a page snapshot from browser_snapshot), nor does it clarify use cases like reordering items versus moving files, leaving the agent to infer context from sibling tool names alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lewisvoncken/playwright-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server