Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

retryMaestroRun

Retry a failed Maestro run or only a specific failed flow by providing its flow ID, so you can recover failed tests without rerunning the whole suite.

Instructions

Retry a Maestro run, or a single failed flow within it when flowId is given.

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

Input Schema

NameRequiredDescriptionDefault
runIdYesRun ID to retry
flowIdNoRetry only this flow (from getMaestroRunStatus output)
projectIdYesProject ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses only the flowId scoping nuance. Because this is a mutating operation, an agent needs to know whether a retry creates a new run or mutates the existing one, whether it re-executes passed flows, whether it costs a device/minute allocation, and what identifiers it returns — none of which is stated.

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 sentence that is front-loaded with the primary action and qualifies the alternative mode with a clear conditional clause. There is no filler and the discriminating detail (flowId) arrives immediately after the main verb.

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?

With three fully documented parameters and no output schema, the definition captures the input contract adequately. What is missing is the effect of the call: whether the result is a new run identifier, whether the original run is preserved, and any precondition on the run's state.

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 coverage is 100%, so projectId, runId, and flowId are already documented, including the note that flowId comes from getMaestroRunStatus output. The description adds meaningful semantics by tying flowId to a partial retry rather than a full retry, but adds nothing about the required projectId/runId pairing or the numeric range constraints.

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 states a specific verb and resource ("Retry a Maestro run") and adds a precise sub-scope ("a single failed flow within it when flowId is given"). That conditional distinction means an agent can tell the full-run behavior apart from the single-flow behavior from the description alone, though it says nothing about how it differs from re-running via the sibling test tools.

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?

Usage is only implied: the words "Retry" and "single failed flow" hint that this applies after a failure, but there is no explicit when-to-use versus when-to-use-another-tool guidance. The description never says whether the run must be in a finished/failed state before retrying, or when to prefer runMaestroTest over a retry.

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