Skip to main content
Glama
Angeluis001

Playwright MCP

by Angeluis001

browser_drag

Destructive

Drag and drop elements between specified source and target locations in web browsers using Playwright automation.

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 handler function that executes the browser_drag tool logic: resolves locators for start and end elements from the page snapshot, generates corresponding Playwright code, and performs the drag-to action.
    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 browser_drag: startElement/startRef for source, endElement/endRef for target.
    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',
    },
  • The complete definition of the browser_drag tool using defineTool, including 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,
        };
      },
    });
  • Registration of browser_drag by including it in the default export array of tools from snapshot.ts.
    export default [
      snapshot,
      click,
      drag,
      hover,
      type,
      selectOption,
    ];
Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description doesn't contradict. The description adds value by specifying the action involves two elements, but it doesn't elaborate on behavioral traits like potential side effects, error conditions, or interaction constraints beyond what annotations provide.

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, clear sentence that efficiently conveys the core action without unnecessary words. It is front-loaded and appropriately sized for the tool's complexity.

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) and lack of output schema, the description is minimal but adequate. It covers the basic action but doesn't address return values, error handling, or detailed usage context, leaving gaps that annotations partially fill.

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 the schema fully documents all four parameters. The description implies parameters for start and end elements but adds no additional meaning beyond the schema's detailed descriptions of human-readable descriptions and exact references from page snapshots.

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 actionable. However, it doesn't differentiate itself 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 like browser_click or browser_hover, nor does it mention prerequisites such as needing a page snapshot or specific element references. It lacks context about appropriate scenarios or exclusions.

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/Angeluis001/playwright-mcp'

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