Skip to main content
Glama

suno_get_tasks_batch

Check the status of multiple music generation tasks in a single request. Retrieve audio and completion details for up to 50 tasks at once.

Instructions

Query multiple music generation tasks at once.

Efficiently check the status of multiple tasks in a single request.
More efficient than calling suno_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 suno_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
Behavior4/5

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

No annotations are provided, so the description carries full burden. It includes a critical note about intermediate audio_urls being streaming previews and the condition for task completion (state 'complete' and success true). It lacks information on potential errors or rate limits.

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 concise and well-structured: a brief intro, a bulleted usage list, a critical note, and a return summary. Every sentence contributes value.

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?

Given the output schema exists, the description does not need to detail return values. It covers the purpose, usage, and behavioral caveats adequately. However, it could mention handling of invalid task IDs or batch size limits beyond the recommendation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema coverage is 100%, but the description adds the maximum recommended batch size of 50 tasks, which is helpful beyond the schema's description. This adds meaning without redundancy.

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 'Query multiple music generation tasks at once.' It uses a specific verb+resource combination and distinguishes itself from suno_get_task by emphasizing batching efficiency.

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 when-to-use scenarios via a bulleted list and notes it's more efficient than calling suno_get_task multiple times. However, it does not explicitly mention when not to use it (e.g., for a single task).

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