Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadAppAutomateApp

Uploads an Espresso (.apk/.aab) or XCUITest (.ipa) app for App Automate runs and returns the projectId needed to start tests on TestingBot.

Instructions

Upload the app under test for an Espresso (.apk/.aab) or XCUITest (.ipa) run on TestingBot. Returns a projectId for uploadAppAutomateTests and runAppAutomateTest. For Maestro flows use uploadMaestroApp instead.

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

Input Schema

NameRequiredDescriptionDefault
frameworkYesTest framework
localFilePathYesLocal path to the app file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden, and it does disclose the key return value (a projectId) and how it chains into subsequent tools. Gaps remain around auth/credential prerequisites, file size limits, and overwrite behavior on re-upload, which matter for an upload operation.

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?

Three short sentences, front-loaded with the action and supported formats, then the return value, then the exclusion. Nothing is redundant or wasted.

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 two-parameter upload tool with no output schema, the description covers formats, return value, and downstream usage, which is enough to call it correctly. It stops short of operational details like credential requirements or failure behavior.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by mapping each framework value to its accepted file extensions (.apk/.aab for espresso, .ipa for xcuitest), which the raw enum does not convey. It says nothing extra about localFilePath beyond what the schema states.

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

Purpose5/5

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

States a specific verb and resource ('Upload the app under test') and scopes it precisely to Espresso (.apk/.aab) and XCUITest (.ipa) runs on TestingBot. It also names the sibling it is not for ('For Maestro flows use uploadMaestroApp instead'), so an agent can distinguish it from other upload tools without opening a schema.

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

Usage Guidelines5/5

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

The definition gives an explicit exclusion with a named alternative: Maestro flows go to uploadMaestroApp. It also names the downstream consumers (uploadAppAutomateTests, runAppAutomateTest), telling the agent what to do with the result.

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