Skip to main content
Glama

suno_get_task

Retrieve the status and result of a music generation task. Polls until complete, providing audio URLs, titles, lyrics, and metadata when finished.

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 (e.g. URLs from audiopipe.suno.ai). These are STREAMING PREVIEW URLs,
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 duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesThe task ID returned from a generation request. This is the 'task_id' field from any suno_generate_*, suno_extend_*, suno_cover_*, or suno_concat_* tool response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Discloses that intermediate audio URLs may appear during pending state and are streaming previews, not final results. Emphasizes checking state field. However, lacks details on rate limits, authentication, or behavior for invalid task_ids. With no annotations, description carries full burden.

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: purpose, usage, states, critical notes, and returns. Front-loaded with purpose. Slightly verbose with the returns line, but each sentence provides necessary information.

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?

Covers main behavior: polling, state handling, intermediate vs final results. Does not detail error handling beyond 'failed' state or invalid task_id. For a simple polling tool with output schema, it is fairly complete.

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?

Only one parameter (task_id) with 100% schema coverage; schema already describes it well. The description reiterates the origin but adds minimal extra value. Baseline 3 is appropriate.

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?

The description clearly states the tool queries status and results of a music generation task. It uses a specific verb-resource pair. However, it does not explicitly differentiate from sibling tools like suno_get_tasks_batch, though the name and context imply distinction.

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?

Provides explicit 'Use this when:' with bullet points, details task states (pending, processing, complete, failed) with clear instructions to keep polling until 'complete'. Also includes a critical note about not stopping on intermediate audio URLs. No when-not-to-use, but the context is very 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/SunoMCP'

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