Skip to main content
Glama

browser_drag

Destructive

Drag and drop elements between specified source and target locations on web pages for 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

  • Handler function for the browser_drag tool. It resolves locators for source and target elements, executes the drag operation using Playwright locators, waits for completion, and adds the equivalent code snippet to the response.
    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)});`);
    },
  • Schema definition for the browser_drag tool, including input schema with start/end element descriptions and refs, validated using Zod.
    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 browser_drag tool is registered using defineTabTool, which defines its capability, schema, and handler.
    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)});`);
      },
    });
  • src/tools.ts:36-52 (registration)
    All tools, including browser_drag from snapshot module, are collected in the allTools array for use in the MCP server.
    export const allTools: Tool<any>[] = [
      ...common,
      ...console,
      ...dialogs,
      ...evaluate,
      ...files,
      ...install,
      ...keyboard,
      ...navigate,
      ...network,
      ...mouse,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs,
      ...wait,
    ];
Behavior3/5

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

Annotations already provide key behavioral traits: readOnlyHint=false (implies mutation), destructiveHint=true (implies changes state), and openWorldHint=true (implies dynamic environment). The description adds the specific action of drag-and-drop, which is useful context beyond annotations. However, it doesn't disclose additional behavioral details like what gets destroyed, potential side effects, or error conditions.

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, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the core action.

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 browser interaction with 4 required parameters) and rich annotations, the description is minimally adequate. However, with no output schema and incomplete behavioral context (e.g., no mention of what happens after drag-and-drop or error handling), it leaves gaps that could hinder effective tool selection and invocation.

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 4 parameters (startElement, startRef, endElement, endRef). The description doesn't add any meaningful parameter semantics beyond what the schema already provides, such as explaining the relationship between 'element' and 'ref' parameters or usage examples.

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 a specific verb+resource combination. However, it doesn't explicitly distinguish this 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), when not to use it, or how it differs from other browser interaction tools like browser_click or browser_hover for similar UI tasks.

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

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