Skip to main content
Glama

suno_get_task

Check if a music generation task has finished and, when complete, retrieve the generated audio URLs, title, lyrics, and other metadata.

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 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 suno_generate_*, suno_extend_*, suno_cover_*, or suno_concat_* 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 fully carries the behavioral disclosure burden. It explains the task state machine (pending, processing, complete, failed) and crucially warns that intermediate audio_url values during 'pending' are streaming previews, not final results. This is critical behavioral context that goes far beyond a simple status check.

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 well-structured with clear sections ('Use this when', 'Task states', 'CRITICAL', 'Returns') and every sentence adds value. The critical warning is essential and not verbose. It is efficiently organized and front-loaded.

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?

The tool is relatively simple but has a tricky polling behavior. The description covers all necessary context: when to use, state meanings, the streaming preview pitfall, and a summary of returned data. The presence of an output schema means return values need not be detailed, and the description adequately addresses the tool's complexity.

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 input schema already includes a thorough description of task_id, including its origin from various generation tools (100% schema coverage). The tool description does not add any additional parameter-level semantics beyond what the schema provides, so the baseline of 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?

The description clearly states the tool's function with a specific verb and resource: 'Query the status and result of a music generation task.' It distinguishes itself from siblings by focusing on checking completion and retrieving audio URLs and metadata, which is not the purpose of generation, deletion, or batch tools.

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 explicitly lists three 'Use this when' scenarios, providing clear context for when to invoke the tool. It does not mention alternatives or when not to use it (e.g., batch retrieval via suno_get_tasks_batch), which prevents a score of 5.

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