Skip to main content
Glama

suno_get_task

Check Suno AI music generation task status and retrieve completed audio URLs, song titles, lyrics, and 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
- 'complete': Generation finished successfully
- 'failed': Generation failed (check error message)

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?

No annotations provided, so description carries full burden. Documents complete task state machine (pending/complete/failed) and error handling guidance ('check error message'). Describes return payload structure (URLs, title, lyrics, duration) supplementing the output schema. Does not mention rate limits or idempotency.

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?

Excellent structure with clear visual hierarchy: purpose statement, usage bullet points, task states enumeration, and return value summary. Every sentence provides distinct value (purpose, usage conditions, state definitions, output preview). No redundancy.

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?

Comprehensive for an async task polling tool. Documents lifecycle states and return values despite presence of output schema. Could enhance by mentioning typical polling patterns or relationship to suno_get_tasks_batch for bulk operations, but adequately complete for single-task retrieval.

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% with detailed description of 'task_id' parameter ('The task ID returned from a generation request...'). Description mentions 'previous generation' implicitly referencing the parameter but does not add syntax or format details beyond schema. Baseline 3 appropriate given schema does heavy lifting.

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?

Opens with specific verb 'Query' and clear resource 'status and result of a music generation task'. Explicitly distinguishes from generation siblings (suno_generate_*, suno_extend_*, etc.) by stating this retrieves results from 'previous generation' rather than creating new content.

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?

Provides explicit 'Use this when:' section with three specific scenarios (checking completion, retrieving URLs, getting full details). Lacks explicit mention of sibling alternative suno_get_tasks_batch for batch operations, but otherwise excellent positive guidance.

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/MCPSuno'

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