Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getMaestroRunResults

Retrieve final results for a completed Maestro run, including per-flow outcomes with failures first, error messages, video links, and the JUnit XML report.

Instructions

Get the final results of a completed Maestro run: per-flow outcomes (failures first, with error messages and video links) plus the JUnit XML 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": {
      "projectId": "<projectId>",
      "runId": "<runId>"
    },
    "name": "getMaestroRunResults"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/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 behavioral burden. It does well on return semantics — failure-first ordering, error messages, video links, JUnit XML — but says nothing about prerequisites (auth scope), size limits, or whether it errors versus returns partial data for an incomplete run.

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?

A single front-loaded sentence with a tight colon-delimited payload list; every clause (failure ordering, error messages, video links, JUnit XML) conveys distinct information an agent would want before calling.

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?

There is no output schema, so the description must describe the return value, and it does so concretely for a two-parameter read tool. The only gap is the behavior on non-completed runs, which matters given the explicit 'completed' qualifier.

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 both parameters (runId, projectId) are already documented in the schema, and the description adds no additional meaning such as ID format or where to obtain them. Baseline 3 applies when structured fields do the heavy lifting.

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 and resource ('Get the final results of a completed Maestro run') and enumerates the payload (per-flow outcomes, error messages, video links, JUnit XML). The word 'completed' implicitly separates it from getMaestroRunStatus and 'Maestro' from getAppAutomateRunResults, but neither sibling is named explicitly.

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 phrase 'completed Maestro run' implies when to call it (after the run finishes) and implies the status tool should be polled beforehand, but that alternative is never named and there is no statement about what happens if the run is still in progress or was cancelled.

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