Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

uploadMaestroFlows

Upload Maestro flow YAML files for a project from a directory, ZIP, or inline content, replacing previously uploaded flows.

Instructions

Upload Maestro flow YAML files for a project. Accepts a local directory (all .yaml/.yml files, preserving structure), a pre-built .zip, or inline flow content. Replaces any previously uploaded flows for the project.

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

Input Schema

NameRequiredDescriptionDefault
flowsNoInline flow files to upload instead of flowsPath
flowsPathNoLocal path to a directory containing flow YAML files, or to a .zip of flows
projectIdYesProject ID returned by uploadMaestroApp

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?

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that previously uploaded flows for the project are replaced, which is important destructive context, but it omits permissions, validation behavior, partial-failure handling, and whether the replacement is atomic.

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?

The description is two compact sentences with the purpose front-loaded and the accepted input modes and replacement behavior following immediately. There is no filler or redundant restatement.

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?

For a three-parameter upload tool with no annotations and no output schema, the description covers the main invocation modes and the replacement side effect. It still leaves gaps around what is returned, how failures or invalid flow files are handled, and whether any prerequisites apply.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is complete, so the baseline is 3, but the description adds meaningful semantics beyond the schema by explaining that flowsPath can be a directory of .yaml/.yml files with preserved structure or a pre-built .zip. It also clarifies the three input modes for providing flows, though it does not elaborate on projectId beyond the schema.

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?

The description states a specific verb and resource: uploading Maestro flow YAML files for a project. It also clarifies the supported input forms, making it distinguishable from sibling upload tools that handle app binaries or companion apps.

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?

It explains the accepted input modes (directory, zip, inline content), which implies when the tool is appropriate. However, it does not explicitly contrast this tool with siblings such as uploadMaestroApp or uploadAppAutomateTests, nor does it state preconditions or exclusions.

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