Skip to main content
Glama
nzjami

Playwright MCP

by nzjami

browser_drag

Destructive

Drag and drop elements in browser automation to simulate user interactions for testing or workflow 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

  • Full definition of the browser_drag tool including its handler. The handler resolves locators for source and target elements using tab.refLocators, executes the drag operation inside waitForCompletion, sets snapshot inclusion, and adds the generated Playwright code to the response.
    const drag = defineTabTool({
      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 (tab, params, response) => {
        response.setIncludeSnapshot();
    
        const [startLocator, endLocator] = await tab.refLocators([
          { ref: params.startRef, element: params.startElement },
          { ref: params.endRef, element: params.endElement },
        ]);
    
        await tab.waitForCompletion(async () => {
          await startLocator.dragTo(endLocator);
        });
    
        response.addCode(`await page.${await generateLocator(startLocator)}.dragTo(page.${await generateLocator(endLocator)});`);
      },
    });
  • Input/output schema (using Zod) for the browser_drag tool, defining parameters for start and end elements.
    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',
    },
  • src/tools.ts:36-52 (registration)
    Central registration of all tools by importing and spreading modules like snapshot (which exports browser_drag) into the allTools array. filteredTools is used by backends to get available tools.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
  • MCP ServerBackend implementation that uses filteredTools to set available tools, exposes their schemas via tools(), and dispatches to individual tool.handle in callTool.
    tools(): mcpServer.ToolSchema<any>[] {
      return this._tools.map(tool => tool.schema);
    }
    
    async callTool(schema: mcpServer.ToolSchema<any>, parsedArguments: any) {
      const response = new Response(this._context, schema.name, parsedArguments);
      const tool = this._tools.find(tool => tool.schema.name === schema.name)!;
      await tool.handle(this._context, parsedArguments, response);
      if (this._sessionLog)
        await this._sessionLog.log(response);
      return await response.serialize();
    }
Behavior3/5

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

Annotations indicate this is a destructive, non-read-only operation with open-world hints, which the description doesn't contradict. However, the description adds minimal behavioral context beyond annotations—it mentions the drag-and-drop action but doesn't detail effects like UI changes, error handling, or interaction constraints. With annotations covering safety and scope, the description provides some value but is not rich in behavioral details.

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 with no wasted words. It's front-loaded with the core action and efficiently conveys the essential purpose without unnecessary elaboration.

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 (destructive interaction with four required parameters) and lack of output schema, the description is minimal but adequate. It covers the basic action but doesn't address outcomes, error cases, or integration with sibling tools like browser_snapshot for obtaining references. With annotations providing safety and scope hints, it's passable but could be more comprehensive.

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 parameters are well-documented in the schema. The description doesn't add any semantic details beyond implying two elements are involved, which is already clear from the parameter names. This meets the baseline for high schema coverage without enhancing parameter understanding.

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 explicitly differentiate from sibling tools like browser_click or browser_hover, which also involve element interaction but with different behaviors.

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 element references. It lacks context about typical use cases 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/nzjami/mcpPlaywright'

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