Skip to main content
Glama

suno_wait_for_songs

Monitor song generation progress and retrieve URLs when complete by specifying song IDs and optional timeout.

Instructions

Wait for songs to complete generation and return their URLs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesArray of song IDs to wait for
timeoutNoMaximum time to wait in seconds (default: 180)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions waiting for completion and returning URLs, but fails to describe key traits like whether it polls continuously, handles partial completions, or what happens on timeout. This leaves significant gaps in understanding the tool's behavior.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for its function, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a waiting/polling tool with no annotations and no output schema, the description is insufficient. It doesn't explain the return format (e.g., structure of URLs, error handling), behavioral details like polling intervals, or how it integrates with sibling tools, leaving the agent with incomplete context.

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 schema description coverage is 100%, so the input schema already documents both parameters ('ids' and 'timeout') with descriptions and defaults. The description adds no additional meaning beyond what the schema provides, such as explaining the format of 'ids' or typical timeout values, resulting in a baseline score.

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 action ('wait for songs to complete generation') and the outcome ('return their URLs'), which is specific and actionable. However, it doesn't explicitly differentiate from sibling tools like 'suno_check_status' or 'suno_download_song', which might have overlapping functionality, so it misses the highest clarity mark.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as 'suno_check_status' for status checking or 'suno_download_song' for downloading. It lacks context on prerequisites (e.g., after song generation) or exclusions, leaving usage unclear.

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/unforced/suno-mcp'

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