Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getMaestroFlowDetails

Retrieve detailed results for a single Maestro flow—including error messages, step-level JUnit reports, video, screenshots, and device logs—to diagnose failures before retrying.

Instructions

Get the detailed result of a single Maestro flow: error messages, step-level JUnit report, and links to the video, screenshots, and device logs. Use this to diagnose why a flow failed before fixing it and calling retryMaestroRun.

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>",
      "flowId": "<flowId>"
    },
    "name": "getMaestroFlowDetails"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID
flowIdYesFlow ID (from getMaestroRunStatus output)
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/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 does disclose the return shape (error messages, step-level JUnit report, links to video, screenshots, device logs) and the read-only nature is implied by 'Get', but it says nothing about artifact retention, whether the flow must have finished before details exist, or any access requirements.

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, zero waste. The payload is front-loaded in sentence one and the actionable guidance in sentence two, with no restatement of the tool name.

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?

With no output schema and no annotations, the description must describe what comes back, and it does list the key artifacts. For a simple three-ID read of moderate complexity, the only gap is lifecycle detail such as whether details are available mid-run.

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?

All three required parameters are fully documented in the schema (100% coverage), including the hint that flowId comes from getMaestroRunStatus output. The description adds no further parameter meaning, so the baseline of 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 uses a specific verb ('Get') and a precisely scoped resource ('the detailed result of a single Maestro flow'), then enumerates the payload (error messages, step-level JUnit report, artifact links). It implicitly distinguishes itself from run-level siblings like getMaestroRunResults by emphasizing 'a single flow', though it never names that contrast explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the decision context directly: use this to diagnose why a flow failed, and it sequences the follow-up action ('before fixing it and calling retryMaestroRun'). That gives the agent both a trigger condition and the next step in the workflow.

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