Skip to main content
Glama
AceDataCloud

Maestro MCP Server

Official
by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

maestro_get_task

Retrieve live progress and final outputs for a Maestro video task by task ID. Use compact mode for a bounded status summary without full brief or progress log.

Instructions

Get live progress and final outputs for one Maestro video task.

Input Schema

NameRequiredDescriptionDefault
compactNoReturn a bounded status and output summary without the full brief or progress log.
task_idYesTask ID returned by maestro_create_video.

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 a bounded status and output summary without the full brief or progress log.",
+  "title": "Compact",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden. It does add real value by signaling the tool returns both 'live progress' (in-flight) and 'final outputs' (terminal), which tells the agent it is safe to poll. It says nothing about auth requirements, rate limits, or failure behavior.

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 front-loaded sentence with zero filler; the verb and scope lead and every word earns its place.

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 an output schema that already defines return values, the description covers purpose and the dual live/final nature adequately. It could be slightly richer on usage routing against maestro_list_tasks, but nothing essential is missing.

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 the schema already documents both task_id and compact, including the fact that compact suppresses the full brief and progress log. The description adds no parameter-level meaning 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 and resource ('Get ... for one Maestro video task') plus the payload ('live progress and final outputs'), which clearly separates it from the sibling list/create tools. It is clear without explicitly naming those siblings, so it lands at 4 rather than 5.

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?

The phrase 'for one Maestro video task' and the singular scope imply this is the single-task retrieval path versus maestro_list_tasks, but no when-to-use, when-not-to-use, or prerequisites are stated. Usage is only implied, not spelled out.

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