Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

listMaestroRuns

List Maestro test runs across all projects, newest first, or look up runs by build/run name. Returns projectId and runId pairs for retrieving run status and results.

Instructions

List Maestro runs across all projects (newest first), or look up runs by their build/run name. Returns projectId + runId pairs for use with getMaestroRunStatus and getMaestroRunResults.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listMaestroRuns"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of runs to retrieve (default: 10, max: 100; ignored with buildName)
offsetNoOffset for pagination (default: 0; ignored with buildName)
buildNameNoLook up runs with this exact run name instead of listing all runs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.9/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 disclosure burden; it does well by declaring the read-only nature implicitly, the ordering ('newest first'), and the exact return shape ('projectId + runId pairs'). It does not mention pagination limits, result caps, or permission/access requirements, which are relevant for a cross-project listing tool.

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 compact sentences that front-load the primary behavior (listing) before the alternate lookup mode and the return contract. Every clause carries information; nothing is padded, though the mid-sentence 'or' construction slightly blurs the primary/secondary relationship.

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?

For a three-optional-parameter listing tool with no output schema, the description covers what an agent needs: scope, ordering, return shape, and the correct follow-up tools. Only minor operational details (pagination behavior, whether results are capped across projects) are absent, and the schema covers most of that.

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 count, offset, and buildName are already fully documented, including the note that count/offset are ignored when buildName is set. The description restates the build-name lookup mode but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Maestro runs') plus the scope ('across all projects') and the ordering ('newest first'), and distinguishes itself from the sibling tools that consume its output (getMaestroRunStatus, getMaestroRunResults). An agent can tell exactly what this returns versus what those return.

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

Usage Guidelines4/5

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

Gives two clear modes of use — broad listing or lookup by exact run/build name — and explicitly routes the agent downstream to the status and results tools once IDs are obtained. It stops short of stating when not to use it (e.g. single-run detail), but the routing makes the boundary implicit and clear.

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