Skip to main content
Glama
jegriffi91

Mobile Automator MCP Server

by jegriffi91

Run Unit Tests

run_unit_tests
Idempotent

Runs unit tests for iOS or Android projects, returning pass/fail counts, failing test names, and error messages.

Instructions

Run the unit-test target for the project. Returns structured results: pass/fail counts, failing test names, first-line failure messages. Long-running — default timeout 30 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moduleNoAndroid only: Gradle module name. Default: "app".
schemeNoiOS only: Xcode scheme name. Required for iOS.
variantNoAndroid only: Build variant (e.g., "debug", "release"). Default: "debug".
platformYesTarget mobile platform
testPlanNoiOS only: Optional xcodebuild -testPlan name to run a specific test plan.
timeoutMsNoMax test-run duration in ms. Default: 1800000 (30 minutes).
gradleTaskNoAndroid only: Explicit Gradle task (e.g., "test", "connectedCheck"). Default: test<Variant>UnitTest (derived from variant).
testFilterNoAndroid only: Value forwarded to `--tests` (e.g., "com.example.MyTest" or "com.example.*"). Omit to run all tests.
destinationNoiOS only: xcodebuild -destination value. Defaults to the iOS Simulator for the first matching runtime.
onlyTestingNoiOS only: Array of test identifiers to restrict the run. Each entry maps to xcodebuild -only-testing:<Target>/<Class>[/<Method>].
projectPathNoAbsolute path to the project. iOS: .xcodeproj (required if workspacePath omitted). Android: Gradle project root containing ./gradlew (required).
configurationNoiOS only: Build configuration (e.g., "Debug", "Release"). Default: "Debug".
workspacePathNoiOS only: Absolute path to a .xcworkspace. Takes precedence over projectPath.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
outputYesTruncated stdout/stderr from the test run
passedYesTrue when the run finished cleanly with zero failing tests
failuresYesFailing tests with first-line messages (may be empty)
platformYes
reportDirNoAndroid only: directory containing the JUnit XML reports that were parsed
durationMsYesTotal test-run wall clock time in ms
totalTestsYesTotal tests executed
failedTestsYesTests that failed
passedTestsYesTests that passed
skippedTestsNoTests reported as skipped, if the tool emits that information
resultBundlePathNoiOS only: path to the .xcresult bundle written by xcodebuild
Behavior4/5

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

Disclosures beyond annotations: returns structured results with specific fields, and describes long-running nature with default timeout. Idempotent and non-destructive nature consistent; no contradictions.

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: first states purpose, second adds behavioral detail. No unnecessary words, properly front-loaded.

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?

Adequate for a complex tool with 13 parameters; output schema covers return structure. Could explicitly note platform-specific param requirements, but schema per-param descriptions fill the gap.

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 covers all parameters (100% coverage), so baseline is 3. Description does not add additional parameter-level meaning; agent must rely entirely on schema for parameter details.

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?

Clearly states verb ('Run') and resource ('unit-test target'), and distinguishes from sibling 'run_feature_test' by specifying it's for unit tests. Also mentions return structure.

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?

No explicit when-to-use or when-not-to-use guidance nor alternatives. However, naming implies purpose and context signals show many sibling tools; a brief differentiation could improve clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jegriffi91/mobile-automator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server