Skip to main content
Glama
AceDataCloud

Maestro MCP Server

Official
by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

maestro_list_tasks

Retrieve recent Maestro tasks owned by the authenticated user, with options to limit results, filter by creation time, and return compact summaries.

Instructions

List recent Maestro tasks owned by the authenticated user.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of recent tasks to return.
compactNoReturn bounded task summaries instead of complete briefs and progress logs.
created_at_maxNoOnly include tasks created strictly before this Unix timestamp.
created_at_minNoOnly include tasks created strictly after this Unix timestamp.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.6
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Return bounded task summaries instead of complete briefs and progress logs.",
+  "title": "Compact",
+  "type": "boolean"
+}
  2. Addedv0.1.4
  3. Removedv0.1.2
  4. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'List' implies a read operation and the ownership scoping is useful, but the description says nothing about ordering, default page size, truncation/pagination behavior, or what 'recent' bounds — all of which are left to the schema's defaults.

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?

A single sentence with no filler, and the scope qualifier is front-loaded. It is efficient, though the extreme brevity is what leaves the guidelines and behavioral gaps noted elsewhere.

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?

An output schema exists, so return values need not be explained, and all parameters are documented at 100% coverage. For a simple read-only listing tool the description is close to sufficient; it only lacks guidance on when this method is preferable to its siblings.

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 all four optional parameters (limit, compact, created_at_min/max) are fully documented in the schema itself. The description adds no filtering or formatting detail beyond that, so the baseline 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?

States a specific verb (List) and resource (Maestro tasks) and narrows scope to 'recent' and 'owned by the authenticated user', which distinguishes it from maestro_get_task. It does not, however, explicitly contrast itself with either sibling or state what 'recent' means operationally.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as maestro_get_task for a single task or maestro_create_video for a new job. The user must infer that this is the browsing/enumeration entry point purely from the name.

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

Deploy Server

Other Tools