Skip to main content
Glama

browser_file_upload

Upload files to web applications through automated browser sessions managed by a dynamic pool system.

Instructions

Upload files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsNo

Implementation Reference

  • index.js:452-458 (registration)
    Registration of the 'browser_file_upload' tool in the MCP server. It uses proxyToolCall to delegate the execution to a browser instance.
    server.tool('browser_file_upload', 'Upload files', {
      paths: z.array(z.string()).optional()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_file_upload', args);
    });
  • The helper function responsible for proxying the tool call to the active browser instance via the MCP client.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
        log(`[proxyToolCall] Result type: ${typeof result}`);
        log(`[proxyToolCall] Result: ${JSON.stringify(result).slice(0, 500)}`);
    
        // The SDK returns { content: [...], isError?: boolean }
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose whether this requires an active file input element, how it handles the browser's native file picker, what validation occurs on paths, or return behavior.

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?

While not verbose, the brevity constitutes under-specification rather than effective conciseness. Two words are insufficient for a browser automation tool with behavioral complexity.

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

Completeness1/5

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

Severely inadequate for a browser automation tool. No mention of browser context, DOM interaction requirements, file input targeting mechanism, or sibling tool relationships. The single optional parameter with no documentation leaves critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage for the 'paths' parameter. Description minimally implies these are file paths but fails to specify they are local filesystem paths, required format (absolute vs relative), or that the parameter is optional despite being an upload tool.

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

Purpose2/5

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

Description 'Upload files' is largely tautological, restating the verb 'upload' from the name while dropping the critical 'browser' context. It fails to distinguish from generic file upload tools or clarify this is browser automation.

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

Usage Guidelines1/5

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

Zero guidance provided. No mention of when to use this (e.g., after clicking a file input element), prerequisites, or interaction with the browser dialog/file picker.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server