Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getAppAutomateRunResults

Fetch per-run outcomes and the JUnit XML report for completed Espresso or XCUITest projects; provide runId to retrieve a single XCUITest run's report.

Instructions

Get the results of a completed Espresso/XCUITest project: per-run outcomes plus the JUnit XML report. For XCUITest, pass runId for a single run's report.

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

Input Schema

NameRequiredDescriptionDefault
runIdNoXCUITest only: fetch the JUnit report of this single run
frameworkYesTest framework
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose a real precondition (project must be completed) and roughly what is returned (per-run outcomes plus JUnit XML). It leaves open important behavior: whether the XML is inline or a link, error behavior when the run is incomplete or the runId is wrong, and how large result sets are paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what is returned and followed by the one conditional parameter rule. No filler, though the second sentence duplicates what the runId schema field already says.

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

Completeness3/5

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

For a 3-parameter read tool with no output schema and no annotations, the description covers purpose and a precondition but not the shape of the JUnit XML payload or failure modes. Given the absence of an output schema, one sentence on the return format would have closed 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 description coverage is 100% and the runId schema field already states 'XCUITest only: fetch the JUnit report of this single run', so the description's runId sentence largely restates the schema. The framework enum and projectId gain no additional meaning from the description; baseline 3 applies.

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 ('Get the results of a completed Espresso/XCUITest project') and scopes the payload ('per-run outcomes plus the JUnit XML report'). It implicitly separates itself from status-oriented siblings by requiring a *completed* project, though it never names getAppAutomateRunStatus as the alternative for in-flight runs.

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?

The precondition 'completed' hints at when the tool is usable, and 'For XCUITest, pass runId for a single run's report' gives a conditional use case. There is no explicit routing guidance (e.g., check getAppAutomateRunStatus first) and no statement of when not to call it.

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