Skip to main content
Glama

browser_drag

browser_drag

Drag one interactive browser element onto another to perform drag-and-drop actions, such as moving items, reordering lists, or adjusting sliders.

Instructions

Drag one element from browser_get_interactives onto 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": {
      "tab_id": "<tab_id>",
      "source_element_id": "<source_element_id>",
      "target_element_id": "<target_element_id>"
    },
    "name": "browser_drag"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_idYesChrome tab ID.
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.
source_element_idYes
target_element_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it doesn't say whether the drag is simulated with mouse events or HTML5 drag events, whether it scrolls elements into view, or what a failed drop does — all important for a non-idempotent interaction.

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?

A single front-loaded sentence with zero filler; every clause earns its place by naming the action and the source of the element IDs. It is arguably too terse rather than padded.

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?

For a six-parameter, non-idempotent, open-world browser interaction with no output schema, the definition gives enough to call it (tab, frame, session, two element IDs) but omits drag mechanics, failure behavior, and the nature of the target element, which an agent would need to use it reliably.

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 coverage is 67%, and the description clarifies the origin of source_element_id by pointing at browser_get_interactives, which the schema does not say. It adds nothing about target_element_id (presumably the same source) or about the interaction of frame_id/session_id with the drag.

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?

States a specific verb (drag) and resource (element) plus the direction of the action, and it names the sibling tool (browser_get_interactives) that produces the element IDs, so an agent can tell it apart from click/type tools. It stops short of differentiating the cases where a native drag differs from a plain click-and-hold.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage guidance is the prerequisite that the source element must come from browser_get_interactives; there is no explicit when-to-use versus alternatives such as browser_click or browser_press, and no mention of preconditions like the target needing to be a valid drop zone.

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