Skip to main content
Glama

Drop files or data onto an element

browser_drop
Destructive

Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided. Takes the session_id from open_browser. 0.1¢ a step that runs.

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": {
      "session_id": "<session_id>",
      "target": "<target>"
    },
    "name": "browser_drop"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoData to drop, as a map of MIME type to string value (e.g. {"text/plain": "hello", "text/uri-list": "https://example.com"}).
pathsNoAbsolute paths to files to drop onto the element.
targetYesExact target element reference from the page snapshot, or a unique element selector
elementNoHuman-readable element description used to obtain permission to interact with the element
session_idYesThe session id open_browser returned.

Output Schema

NameRequiredDescriptionDefault
urlNoThe address of the page after the step.
errorNoWhy the step failed, when it failed.
titleNoThe page title.
read_atNoWhen the page was read.
took_msNoHow long the step took.
price_usdNoWhat the step cost, in dollars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "The page after the step, and what the step cost.",
      +  "properties": {
      +    "error": {
      +      "description": "Why the step failed, when it failed.",
      +      "type": "object"
      +    },
      +    "price_usd": {
      +      "description": "What the step cost, in dollars.",
      +      "type": "number"
      +    },
      +    "read_at": {
      +      "description": "When the page was read.",
      +      "type": "string"
      +    },
      +    "title": {
      +      "description": "The page title.",
      +      "type": "string"
      +    },
      +    "took_ms": {
      +      "description": "How long the step took.",
      +      "type": "integer"
      +    },
      +    "url": {
      +      "description": "The address of the page after the step.",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive, non-idempotent, and open-world behavior, so the description's real contribution is the per-step cost (0.1¢) and the session dependency from open_browser. It does not explain what state the drop mutates or that permission is granted via the element description parameter, which is a modest remaining gap given the annotations.

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?

Four short sentences, each carrying distinct information: action and semantics, a constraint, an external dependency, and a cost. The scoping and constraint information is front-loaded with no filler or repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full schema, an output schema, and rich annotations, the description only needs to add the non-structured facts, and it does: the mutual-exclusivity rule, session provenance, and cost. What is missing is failure behavior (e.g., what happens if a path is invalid or the element is not a drop target), which would be useful for a destructive action.

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 100%, so paths, data, target, element, and session_id are already documented, establishing the baseline of 3. The description does add the cross-parameter constraint that at least one of paths or data must be supplied, which the schema alone cannot express since neither is individually required, but it adds nothing about the remaining parameters.

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 uses a specific verb and resource ("Drop files or MIME-typed data onto an element") and clarifies the semantics with "as if dragged from outside the page," which separates it from an in-page drag. It does not name the nearest sibling (browser_file_upload, browser_drag) explicitly, so an agent still has to infer the boundary.

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?

It gives one hard usage rule (at least one of paths or data) and says the session_id comes from open_browser, which is genuinely actionable. However, it never states when to prefer this over browser_file_upload or browser_drag, nor any preconditions about the element being a valid drop target, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.