Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ACEDATACLOUD_API_TOKENYesYour Ace Data Cloud API token. Get one from https://platform.acedata.cloud/console/applications

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
maestro_get_taskA

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

maestro_list_tasksB

List recent Maestro tasks owned by the authenticated user.

maestro_create_videoA

Create a complete video or iterate on a prior Maestro video.

One task delivers one video in one language. Successful jobs cost 0.7 Credits per actual
delivered second, never above the requested duration, with no scenario or language surcharge.
Failed jobs and task polling are free.

The call returns immediately with a task_id. Use maestro_get_task to monitor progress and obtain
the completed video's output_url, captions_url, cover_url, duration, and QC score.

Prompts

Interactive templates invoked by user choice

NameDescription
maestro_video_workflowExplain the recommended Maestro workflow.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct action on the same resource: create a video task, fetch one task, list tasks. The descriptions reinforce the boundaries (create returns a task_id, get_task consumes it), leaving no realistic chance of misselection.

Naming Consistency5/5

All three tools use the same maestro_ prefix followed by a consistent verb_noun pattern (create_video, get_task, list_tasks). Fully predictable and readable.

Tool Count4/5

Three tools is on the lean side but each earns its place in the create-then-poll-then-list workflow for a narrow video-generation API. No filler or redundant tools are present.

Completeness4/5

The core lifecycle (submit job, poll progress, retrieve outputs, list history) is covered with no dead ends for the happy path. Minor gaps exist around cancelling/deleting a task and checking credit balance, which agents must work around.

Maintenance

ActivityNo data
ResponsivenessOutdated data