Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

drag

Simulates a pointer movement from a source CSS selector to a target selector, enabling element-to-element drop actions in a specified browser tab.

Instructions

Drag from one element/position to another

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": {
      "sourceSelector": "<sourceSelector>",
      "targetSelector": "<targetSelector>"
    },
    "name": "drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
sourceSelectorYesCSS selector of element to drag
targetSelectorYesCSS selector of drop target

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about how the drag is performed (native HTML5 drag events vs. synthetic mouse moves), whether it waits for completion, or what happens if the selectors are missing. For an automation action as failure-prone as drag-and-drop, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, which is good. But its brevity comes at the cost of substance rather than being genuinely concise, since the one clause is also imprecise.

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?

With no annotations, no output schema, and a behaviorally complex interaction, the description should explain at least the drag mechanism and expected outcome. It leaves everything beyond the bare action unstated.

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 tabId, sourceSelector, and targetSelector are already fully documented in the schema, setting the baseline at 3. The description adds no format or constraint detail, and its mention of 'position' slightly conflicts with the selector-only parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'drag' is specific and the resource is named, so an agent can tell this is a drag-and-drop interaction. However, 'element/position' is vague and actually mismatched with the schema, which accepts only CSS selectors and no coordinates, and nothing distinguishes it from siblings like click or hover.

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?

There is no guidance on when to use this tool versus click, hover, or execute_javascript, and no prerequisites such as requiring the page to be loaded or the elements to be visible. The agent must infer all usage context from the name alone.

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