Skip to main content
Glama

suno_get_tasks_batch

Query multiple music generation tasks simultaneously to verify status and retrieve final audio when tasks are complete.

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 provided, so description carries full burden. Discloses that intermediate audio_url during pending is a preview, not final. Mentions maximum batch size of 50 (reinforced from schema). However, lacks details on rate limits or authentication needs.

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 clear sections (purpose, when to use, critical note). The 'Returns' section is somewhat redundant with output schema but not overly verbose. Could be slightly more concise.

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 output schema exists, description covers essential behavioral context, usage scenarios, and critical caveats. Differentiates from sibling suno_get_task. Could mention that this is a read-only polling tool, but overall sufficient.

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 covers 100% of parameter description, so baseline is 3. Description adds context about efficiency and state handling but does not enhance the meaning of task_ids beyond what schema already provides.

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?

Description clearly states 'Query multiple music generation tasks at once' and explicitly distinguishes from sibling suno_get_task by noting it is more efficient than calling that tool multiple times.

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 when-to-use scenarios (multiple pending generations, batch status). Includes critical note about state handling shared with suno_get_task. Does not explicitly mention when not to use (e.g., single task), but this is implied.

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