Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

upload_file

Uploads one or more local files to a file input element matched by a CSS selector, with optional tab targeting for browser automation.

Instructions

Upload file(s) to a file input element

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": {
      "selector": "<selector>",
      "files": "<files>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesArray of absolute file paths to upload
tabIdNoTab ID (optional)
selectorYesCSS selector of the <input type="file"> element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.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 disclosure burden for a mutation tool. It does not say whether files must exist locally, whether the selector must resolve before upload, whether a change event is dispatched, whether multiple files in the array are supported by the target input, or what happens on failure — all meaningful behavior for an upload tool.

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 short sentence with no wasted words and the core action front-loaded. It is arguably under-specified rather than verbose, so the economy is a virtue but does little to help the agent beyond the title.

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 3-parameter tool with complete schema coverage and no output schema, the description is minimally adequate: the parameters are self-explanatory. However, with no annotations and no guidance on element requirements or side effects, an agent facing a non-trivial file-input interaction lacks the context needed to call it confidently.

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 all three parameters (selector, files, tabId) are already documented in the input schema. The description's 'file(s)' hints at the array semantics but adds no new meaning beyond what the schema provides; baseline 3 applies.

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 states a specific verb and resource — upload file(s) to a file input element — which is concrete and immediately actionable. It does not explicitly contrast itself with siblings like fill or fill_form, but the phrase 'file input element' narrows its scope enough that an agent can tell it is not a generic form-fill tool.

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 fill/fill_form, nor any stated preconditions such as the element needing to be an <input type="file"> that is present and visible. The agent must infer everything about applicability from the single phrasing in the description.

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