Problem
The MCP can inspect a known build or session, but cannot list historical Automate/App Automate executions for a project.
Given a project name, an agent cannot determine whether a test:
- failed for the first time,
- has failed consistently for several days, or
- is intermittently flaky.
listBuildId returns only the latest matching build, while
listTestRuns belongs to Test Management rather than Automate execution history.
Proposed tool
listExecutionHistory({
projectName,
testName?,
since?,
limit?,
status?
})
Useful response fields:
- build name and API build ID
- execution timestamp and status
- test name and test ID
- session ID and session type
- platform/device
- failure summary
- is_flaky, is_new_failure, and is_always_failing
- Observability and App Automate URLs/identifiers
It would also be helpful to resolve a dashboard build URL into its
Observability build ID and related App Automate sessions.
Use case
Allow an MCP agent to triage a failed test and distinguish a new regression
from a recurring or one-off failure.
Problem
The MCP can inspect a known build or session, but cannot list historical Automate/App Automate executions for a project.
Given a project name, an agent cannot determine whether a test:
listBuildIdreturns only the latest matching build, whilelistTestRunsbelongs to Test Management rather than Automate execution history.Proposed tool
Useful response fields:
It would also be helpful to resolve a dashboard build URL into its
Observability build ID and related App Automate sessions.
Use case
Allow an MCP agent to triage a failed test and distinguish a new regression
from a recurring or one-off failure.