Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadMaestroApp

Upload an APK, AAB, IPA, or zipped .app for Maestro testing on TestingBot; duplicate binaries are skipped and a projectId is returned for flow uploads and test runs.

Instructions

Upload a mobile app (APK, AAB, IPA, or zipped .app) for Maestro testing on TestingBot. Skips the upload if the same binary was uploaded before. Returns a projectId used by uploadMaestroFlows and runMaestroTest.

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": "uploadMaestroApp"
  }
}

Input Schema

NameRequiredDescriptionDefault
localFilePathYesLocal path to the .apk, .aab, .ipa or .zip app file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the entire behavioral burden, and it does disclose two genuinely non-obvious traits: the upload is skipped when an identical binary was already uploaded, and the call returns a projectId. It says nothing about permissions/credentials, file size limits, failure behavior for malformed binaries, or whether the operation blocks until upload completes.

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: capability and formats first, then the dedup behavior, then the return value and downstream consumers. Nothing is redundant and the most decision-relevant fact (it produces a projectId for other tools) is not buried.

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 upload tool this is close to complete: formats, idempotency, and the return value are all stated, so an agent knows what it gets back even without an output schema. The missing piece is operational detail such as size limits or auth expectations, which matters more precisely because no annotations exist to cover them.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is high. The description reinforces it by enumerating the same accepted extensions in prose, helping the agent validate a path before calling, though it adds no path-format guidance (absolute vs relative) beyond the schema.

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 mobile app') plus the accepted artifact formats (APK, AAB, IPA, zipped .app) and the target platform ('for Maestro testing on TestingBot'). It partially differentiates from siblings by naming uploadMaestroFlows and runMaestroTest as consumers, though it never contrasts with uploadMaestroCompanionApp or uploadAppAutomateApp directly.

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

Usage Guidelines4/5

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

Usage context is clear: the file is for Maestro testing and the resulting projectId feeds uploadMaestroFlows and runMaestroTest, which tells the agent where this sits in the workflow. There are no explicit exclusions telling the agent when to pick a different upload tool, so it stops short of full when/when-not guidance.

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