Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAppAutomateRunStatus

Retrieve the status of Espresso or XCUITest runs for a project. Omit runId to list all runs with their state: WAITING, READY, DONE, or FAILED.

Instructions

Get the status of Espresso/XCUITest run(s) for a project. Omit runId to list all runs. Statuses: WAITING, READY (running), DONE, FAILED.

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

Input Schema

NameRequiredDescriptionDefault
runIdNoSpecific run ID to inspect
frameworkYesTest framework
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It helpfully enumerates the possible status values (WAITING, READY, DONE, FAILED) and clarifies the list-vs-single behavior, but says nothing about permissions, pagination on the list mode, or response shape.

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 with zero waste: purpose first, the optional-parameter behavior second, and the result vocabulary last. Every sentence carries information.

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 simple three-parameter read tool with full schema coverage and no output schema, this is nearly complete, especially since the status vocabulary stands in for return-value documentation. Minor gaps remain around list-mode volume and permissions.

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; the description earns above that by explicitly explaining the runId omission case, which adds meaning beyond the schema's 'Specific run ID to inspect' wording. The framework enum values are not re-explained, but the schema already covers them.

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 (get), resource (status of Espresso/XCUITest runs), and scope (for a project). Naming the frameworks effectively separates it from the Maestro status sibling, though it does not explicitly route to that alternative.

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?

'Omit runId to list all runs' gives clear conditional usage for the optional parameter, so the two modes are distinguishable. However, there is no guidance on when to prefer this tool over getAppAutomateRunResults or getMaestroRunStatus, leaving cross-tool selection implied.

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