Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadAppAutomateTests

Uploads an Espresso test APK or zipped XCUITest runner bundle to an App Automate project so mobile tests can run on TestingBot.

Instructions

Upload the test suite for an App Automate project: the instrumented test APK for Espresso, or the zipped XCUITest runner bundle for XCUITest.

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>",
      "projectId": "<projectId>",
      "localFilePath": "<localFilePath>"
    },
    "name": "uploadAppAutomateTests"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkYesTest framework
projectIdYesProject ID returned by uploadAppAutomateApp
localFilePathYesLocal path to the test suite (.apk for Espresso, .zip for XCUITest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.2/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 and does not say whether a repeated upload overwrites or adds a new test suite version, what identifier is returned, whether the file is validated against the declared framework, or any size/timeout limits. It conveys only the file-type expectation, which the annotations do not cover but which the schema largely already states.

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?

A single front-loaded sentence that names the action, the project type, and the two artifacts. Nothing is padded or repetitive.

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

Completeness2/5

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

There is no output schema and no annotations, so the description is the only place to learn what an upload returns (an ID used later by runAppAutomateTest) and how it fits the upload-app-then-upload-tests-then-run sequence. Neither is mentioned, leaving a real gap for a mutation tool in a multi-step workflow.

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 are already documented, including the .apk/.zip expectations. The description reinforces the framework-to-file-type mapping but adds no format, size, or path-syntax detail 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?

States a specific verb (upload) and resource (test suite) and enumerates the exact artifact per framework: instrumented test APK for Espresso, zipped XCUITest runner bundle for XCUITest. It implicitly separates itself from the sibling uploadAppAutomateApp by scoping to the test suite rather than the app, but never names that sibling explicitly.

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?

Usage context is implied by 'for an App Automate project' plus the framework enum, but there is no explicit when-to-use/when-not guidance and no statement of prerequisites such as needing a project created by uploadAppAutomateApp first. That prerequisite lives only in the projectId schema description, not in the tool description.

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