Skip to main content
Glama

browser_drag

Drags between precise viewport coordinates to simulate pointer movement and drag events for canvas, slider, or drag-and-drop interactions.

Instructions

Drag between exact viewport coordinates. DOM mode dispatches pointer and drag events.

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": {
      "tabId": "<tabId>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
tabIdYesTab id from browser_tabs.
expectNoPost-action condition. Default timeout is 1.2 seconds in visible pages and 3 seconds in hidden pages. A mismatch does not undo the action; inspect before retrying.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
inputModeNoAuto uses trusted Chrome text insertion only in the active foreground tab; DOM otherwise. Pointer actions and keys always use DOM.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only states that DOM mode dispatches pointer and drag events — a point the inputMode schema field already makes. It omits coordinate origin relative to scrolling, whether the drag is a single gesture or intermediate moves, what happens on failure or timeout, and the side effects of an untrusted DOM-synthesized drag on real applications.

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

Conciseness4/5

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

Two short sentences, front-loaded with the core action, with no filler. The second sentence largely restates the inputMode enum description, so it earns slightly less than full marks, but nothing is bloated.

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?

Seven parameters including a nested expect object, no annotations, and no output schema make this a complex mutation tool, yet the description is only two sentences. It leaves out failure semantics, scroll/coordinate behavior, and any note about verifying results, which is exactly the context an agent needs before doing a drag.

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 71%, so the structured fields already document tabId, browser, frameId, inputMode and expect. The description does add one genuinely useful clarification — that from/to are exact viewport coordinates rather than selectors or page coordinates — which the schema does not state, but it says nothing about ordering of the pair, scrolling interaction, or the expect object.

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?

Names a specific verb (drag) and a specific resource/input space (exact viewport coordinates), so an agent can tell this is a low-level pointer drag and not a click or hover. However, it never distinguishes itself from sibling pointer tools such as browser_click, browser_move, or browser_hover, which an agent may reasonably consider for the same intent.

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 explicit when-to-use or when-not-to-use guidance, no mention of alternatives (e.g., use click for discrete pointer input, scroll for wheel actions), and no prerequisites such as needing a page/tab ready or requiring the correct inputMode. Usage is only inferable from the tool name and the word 'drag'.

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