Skip to main content
Glama

suno_generate_music

Generate AI songs from text prompts with automatically created lyrics and style. Uses Suno's Inspiration Mode for quick music creation without requiring detailed composition input.

Instructions

Generate AI music from a text prompt using Suno's Inspiration Mode.

This is the simplest way to create music - just describe what you want and Suno
will automatically generate appropriate lyrics, melody, style, and arrangement.

Use this when:
- You want quick music generation with minimal input
- You don't have specific lyrics in mind
- You want Suno to be creative with the arrangement

For full control over lyrics and style, use suno_generate_custom_music instead.

Returns:
    Task ID and generated audio information including URLs, title, lyrics, and duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the music to generate. Be descriptive about genre, mood, instruments, and theme. Examples: 'A happy birthday song with acoustic guitar', 'Epic orchestral battle music with dramatic choir', 'Chill lo-fi hip hop beat for studying'
modelNoSuno model version. 'chirp-v5-5' is the latest and recommended for best quality with 8-minute max duration. 'chirp-v4-5' is a reliable choice for most use cases. Older models (v3, v3-5, v4) have shorter duration limits.chirp-v5-5
instrumentalNoIf true, generate instrumental music without vocals. Default is false (with vocals).
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the audio is generated.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It successfully explains that the tool automatically generates lyrics, melody, style, and arrangement, and specifies the return value structure (Task ID, URLs, title, lyrics, duration). It implies asynchronous behavior via Task ID return, though it doesn't explicitly state processing time or polling requirements.

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 optimally structured with clear sections: core function, simplicity claim, usage conditions, alternative pointer, and return value summary. Every sentence contributes distinct information without redundancy, and the most critical information (the generation mode) is front-loaded in the first sentence.

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?

Given the tool has 100% schema coverage and a declared output schema exists, the description appropriately explains the return values (Task IDs and audio metadata) and differentiates from the primary sibling. The complexity level (4 simple parameters) is well-matched by the description's detail level.

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 description coverage is 100%, establishing a baseline of 3. The description provides semantic context for the 'prompt' parameter ('just describe what you want') but does not add significant meaning for the other three parameters (model, instrumental, callback_url) beyond what the 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?

The description opens with a specific verb-resource combination ('Generate AI music from a text prompt') and explicitly identifies the modality ('Suno's Inspiration Mode'). It clearly distinguishes this tool from siblings by contrasting it with 'suno_generate_custom_music' for users who want 'full control' versus this tool's automatic generation of lyrics and arrangement.

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

Usage Guidelines5/5

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

Provides explicit 'Use this when' bullet points covering minimal input scenarios and lack of specific lyrics. It explicitly names the sibling alternative ('suno_generate_custom_music') for users needing full control, creating a clear decision boundary between the two generation tools.

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