Skip to main content
Glama

producer_get_tasks_batch

Check the status of multiple music generation tasks in one request. Retrieve audio and status info for up to 50 tasks at once.

Instructions

Query multiple music generation tasks at once.

Efficiently check the status of multiple tasks in a single request.
More efficient than calling producer_get_task multiple times.

Use this when:
- You have multiple pending generations to check
- You want to get status of several songs at once
- You're tracking a batch of generations

CRITICAL: Same as producer_get_task — only consider a task complete when its state
is 'complete' and success is true. Intermediate audio_url values during 'pending'
state are streaming previews, NOT final results.

Returns:
    Status and audio information for all queried tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idsYesList of task IDs to query. Maximum recommended batch size is 50 tasks.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided; description carries full burden. Discloses critical behavior: only consider task complete when state is 'complete' and success true; intermediate audio_urls are streaming previews. Mentions recommended batch size. Lacks details on rate limits or error handling, but key info is present.

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?

Description is well-structured with bullet points for usage, a critical warning, and a returns line. It is fairly concise, though could be slightly shorter. The organization aids readability.

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?

Has output schema, so return details are covered. Description covers purpose, usage, and critical behavioral note. Given the tool's simplicity (single parameter), it is mostly complete, but could clarify output structure references to producer_get_task.

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 100%. The description adds value with 'Maximum recommended batch size is 50 tasks' for the task_ids parameter, which is not in the schema. This provides practical usage constraint beyond the schema's type and title.

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 clearly states 'Query multiple music generation tasks at once' and 'Efficiently check the status of multiple tasks', specifying the verb (query/check) and resource (tasks). It distinguishes itself from the sibling tool producer_get_task by emphasizing batch operation.

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

Usage Guidelines5/5

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

Explicitly lists when to use: 'multiple pending generations', 'get status of several songs', 'tracking a batch'. Compares to alternative: 'More efficient than calling producer_get_task multiple times'. Also provides critical guidance about not treating intermediate audio as final.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/ProducerMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server