Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadFile

Upload local APK, IPA, or ZIP files to TestingBot storage for mobile app testing and receive an app_url to use in test runs.

Instructions

Upload a local file (APK, IPA, or ZIP) to TestingBot storage for mobile app testing. Returns an app_url for use in tests.

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": {
      "localFilePath": "<localFilePath>"
    },
    "name": "uploadFile"
  }
}

Input Schema

NameRequiredDescriptionDefault
localFilePathYesLocal path to the file to upload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the destination (TestingBot storage), the accepted formats, and the return value (app_url), which is valuable since there is no output schema. It omits file size limits, auth requirements, overwrite behavior for same-named files, and whether the upload is synchronous — significant gaps for a network upload tool with zero annotation coverage.

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?

Two sentences, both earning their place: the first states the action, formats, and destination; the second states the return value and its purpose. It is front-loaded with no filler.

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?

For a one-parameter tool with full schema coverage, the description covers action, format constraints, destination, and return value. The main missing element is operational limits (size, auth, overwrite), which matter but are secondary for a simple upload.

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

Parameters4/5

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

With a single parameter at 100% schema coverage, the baseline is 3, and the description earns a bump by constraining the value: the path must point to an APK, IPA, or ZIP. That format restriction is real guidance the schema does not encode.

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 gives a specific verb and resource (upload a local file to TestingBot storage) and names the accepted formats (APK, IPA, ZIP) plus the domain (mobile app testing). The word 'local' implicitly contrasts with the sibling uploadRemoteFile, but no sibling is named explicitly, so differentiation is inferential rather than stated.

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 implies when to use it by stating the returned app_url is 'for use in tests', which gives an agent the downstream context. However, there is no explicit when-not guidance, no mention of when to prefer uploadRemoteFile or the app-automate/maestro variants, and no prerequisites such as authentication.

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