Skip to main content
Glama

producer_get_task

Check the state of a music generation task and retrieve final audio URL, title, and lyrics only when 'state' is 'complete'.

Instructions

Query the status and result of a music generation task.

Use this to check if a generation is complete and retrieve the resulting
audio URLs, titles, lyrics, and other metadata.

Use this when:
- You want to check if a generation has completed
- You need to retrieve audio URLs from a previous generation
- You want to get the full details of a generated song

Task states:
- 'pending': Generation is still in progress — KEEP POLLING
- 'processing': Generation is being processed — KEEP POLLING
- 'complete': Generation finished successfully — this is the ONLY state that means done
- 'failed': Generation failed (check error message)

CRITICAL: During the 'pending' state, the response may already contain intermediate
audio_url values (streaming preview URLs). These are NOT final results. You MUST check
the 'state' field — only present the results to the user when state is 'complete' and
success is true. Do NOT stop polling just because audio_url is non-empty.

Returns:
    Task status and generated audio information including URLs, title, lyrics, and task timing metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a generation request. This is the 'task_id' field from any producer_generate_*, producer_extend_*, producer_cover_*, or other tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and does an excellent job. It discloses task states, explicitly states that 'pending' and 'processing' require continued polling, gives the only 'done' state ('complete'), and includes a critical warning about intermediate audio URLs not being final results. This is far beyond basic disclosure.

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?

The description is appropriately sized and front-loaded, starting with the primary purpose. It uses clear sections (Use this when, Task states, CRITICAL) and every sentence contributes necessary information, especially the critical warning about intermediate audio URLs. No wasted words.

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 the tool's complexity (polling semantics, state machine, intermediate data), the description is fully self-contained. It explains the states, the correct completion condition, the trap of intermediate audio URLs, and summarizes the output. With an output schema present, it appropriately does not enumerate return fields in detail.

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?

The schema already provides 100% coverage of the single parameter (task_id), including its provenance from generation tools. The description repeats this information without adding significantly new meaning beyond what the schema already documents, so the baseline of 3 applies.

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 the tool queries the status and result of a music generation task, using a specific verb ('Query') and a specific resource ('a music generation task'). It distinguishes itself from sibling tools by focusing on polling and retrieving individual task results, with explicit use cases listed.

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?

The description provides explicit 'Use this when' scenarios (checking completion, retrieving audio URLs, getting full details). However, it does not explicitly mention when not to use this tool or recommend alternatives like producer_get_tasks_batch for batch operations.

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