Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

runAppAutomateTest

Start an Espresso or XCUITest run on a TestingBot device for app automation, returning a run ID immediately so you can poll status and fetch results.

Instructions

Start an Espresso or XCUITest run on a TestingBot device. Returns immediately with the run ID — it does NOT wait for completion. Poll with getAppAutomateRunStatus, then fetch getAppAutomateRunResults. If the app needs a localhost / private-network backend, start a tunnel first (startTunnel): the run uses the account's newest running tunnel. On Android, point the app at a hostname that resolves to 127.0.0.1 on the tunnel's machine (e.g. myapp.localtest.me), not localhost, which Android never proxies.

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>"
    },
    "name": "runAppAutomateTest"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA name for this test run, shown in the dashboard
buildNoBuild identifier to group runs
localeNoLocale for the run (e.g. "fr_FR")
versionNoOS version (e.g. "14")
packagesNoEspresso only: run only these packages
timeZoneNoTime zone for the run (e.g. "Europe/Brussels")
frameworkYesTest framework
projectIdYesProject ID returned by uploadAppAutomateApp
deviceNameNoDevice name, supports wildcards/regex (e.g. "Pixel 8", "iPhone 1[4-6]", "*"). Default: any device
realDeviceNoRun on a physical device instead of an emulator/simulator
testRunnerNoEspresso only: custom instrumentation runner
annotationsNoEspresso only: run only tests with these annotations
testClassesNoEspresso only: run only these test classes (fully qualified)
skipTestClassesNoEspresso only: skip these test classes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the async/non-blocking behavior, the follow-up polling chain, the implicit selection of the account's newest running tunnel, and the Android localhost proxying caveat. It omits auth requirements, concurrency/queueing limits, and what happens when no tunnel is running, which leaves some behavioral gaps for a resource-consuming run-starter.

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?

Front-loads the core action and the non-blocking caveat in the first sentence, then sequences prerequisites after. Five sentences, each carrying distinct operational information with no repetition of schema content.

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 14-parameter, no-output-schema run launcher, the description covers the call-and-poll workflow and the tunnel precondition well. It could say more about failure modes (invalid projectId, no matching device, tunnel absent) or concurrency behavior, but nothing needed to invoke it correctly is missing.

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 14 parameters including framework, projectId, and the Espresso-only filters are already documented in the schema. The description adds no parameter-level meaning beyond noting the Espresso/XCUITest split, which the framework enum already conveys, so baseline 3 applies.

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 ('Start an Espresso or XCUITest run on a TestingBot device') and immediately bounds the scope to two frameworks, which separates it from the Maestro and accessibility siblings. An agent can tell what this does without opening the 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?

Gives an explicit lifecycle: this returns immediately, then poll with getAppAutomateRunStatus, then fetch getAppAutomateRunResults. It also names a prerequisite and the tool that satisfies it (startTunnel) plus the exact condition that triggers it (localhost/private-network backend).

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