Skip to main content
Glama

producer_get_tasks_batch

Query the status of multiple music generation tasks in a single request to efficiently check batch progress and retrieve final audio URLs when tasks complete.

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
Behavior5/5

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

No annotations provided, so description bears full burden. It discloses critical behavior: task completion condition (state='complete', success=true) and warns that intermediate audio_url values during 'pending' are streaming previews, not final results.

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?

Well-structured with sections and front-loaded purpose. Minor redundancy between 'Efficiently check...' and 'More efficient than...' but overall efficient and easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given simple schema (1 param with full description) and existence of output schema, the description covers functionality, usage context, critical behavioral warnings, and return description. No gaps evident.

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 coverage is 100% for the single parameter 'task_ids', with description already stating batch size limit. The description adds no additional parameter meaning beyond the schema, so baseline 3 is appropriate.

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?

Clearly states it queries multiple music generation tasks, differentiating from sibling producer_get_task by emphasizing batch efficiency. The core action and resource are unambiguous.

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

Usage Guidelines4/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, batch tracking) and notes efficiency advantage over single-task variant. Lacks explicit 'when not to use' but positive guidance is clear.

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