Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

listMaestroProjects

Fetch Maestro projects newest first to view app details, flow names, and run IDs; use the results to find an existing projectId instead of re-uploading an app.

Instructions

List Maestro projects on the account (newest first): app details, flow names, and run IDs. Use this to find an existing projectId instead of re-uploading an app.

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of projects to retrieve (default: 10, max: 100)
offsetNoOffset for pagination (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/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 load. It does disclose the sort order and the fields returned, which signals a read-only listing call, but it says nothing about pagination behavior, result size limits, permission requirements, or what an empty account returns.

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, no filler. The primary action and its returned payload come first, and the routing hint ('instead of re-uploading') is placed after the core description where it belongs.

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 simple two-parameter read tool with no output schema, the description covers what it does, what comes back, and why an agent would call it. The remaining gap is pagination and limit behavior, which is minor given the schema already documents both parameters.

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?

Both parameters (count with a 1-100 range and default 10, offset with default 0) are already fully documented in the schema at 100% coverage, so the baseline is 3. The description adds no extra meaning about how count and offset interact with the 'newest first' ordering.

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 pairs a specific verb and resource ('List Maestro projects on the account') with result content ('app details, flow names, and run IDs') and an ordering guarantee ('newest first'). That makes the operation concrete, though it does not explicitly contrast with nearby list-style siblings such as listMaestroRuns.

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?

It gives an explicit use case: 'Use this to find an existing projectId instead of re-uploading an app.' That covers when to reach for this tool and implies the upload path as the thing to avoid, but there is no statement about when not to use it or which list tool to pick for other needs.

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