Skip to main content
Glama

suno_generate_custom_music

Generate custom AI music by providing your own lyrics with section markers, song title, and music style. Control every aspect of the song creation process.

Instructions

Generate AI music with full control over lyrics, title, and style (Custom Mode).

This gives you complete creative control over the song. You provide the lyrics
with section markers, and Suno generates the melody and arrangement.

Use this when:
- You have specific lyrics you want to use
- You want precise control over the music style
- You need a specific song title
- You want to specify vocal gender (v4.5+ models)
- You want the API to auto-generate lyrics from a prompt (use lyric_prompt)

For quick generation without writing lyrics, use suno_generate_music instead.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lyricNoSong lyrics with section markers. Use [Verse], [Chorus], [Pre-Chorus], [Bridge], [Outro], [Intro] to structure the song. Example: [Verse 1] Walking down the empty street Rain is falling at my feet [Chorus] But I keep moving on Until the break of dawn. Leave empty when using lyric_prompt to auto-generate lyrics.
titleNoTitle of the song. Keep it concise and memorable.
styleNoMusic style description. Be specific about genre, mood, tempo, and instruments. Examples: 'upbeat pop rock, energetic drums, electric guitar', 'acoustic folk, gentle, fingerpicking', 'dark electronic, synthwave, 80s retro'
modelNoSuno model version. 'chirp-v5-5' or 'chirp-v5' recommended for best quality.chirp-v5-5
instrumentalNoIf true, generate instrumental version (lyrics will be ignored). Default is false.
lyric_promptNoPrompt for auto-generating lyrics. Only used when custom is true and lyric is empty. Provide a dict with the lyric generation parameters (e.g. {'prompt': 'A song about winter'}).
style_negativeNoStyles to explicitly exclude from the generation. Examples: 'heavy metal, screaming', 'autotune, electronic'
vocal_genderNoPreferred vocal gender. 'f' for female, 'm' for male, empty string for AI to decide. Only works with v4.5+ models.
variation_categoryNoVariation intensity for v5+ models. 'high' for maximum variation, 'normal' for balanced, 'subtle' for minimal changes. Only supported in chirp-v5 and above.
weirdnessNoAdvanced parameter for custom mode. Controls how unusual/experimental the generation is.
style_influenceNoAdvanced parameter for custom mode. Controls how strongly the style prompt influences the generation.
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
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions creation ('generates') and returns Task ID + audio info, but fails to disclose any side effects, authentication needs, rate limits, or that it consumes credits. For a tool with 12 parameters, this is insufficient behavioral disclosure.

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?

Description is well-structured with bullet points for use cases, a clear sentence about returns, and no redundant information. Every sentence adds 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 12 parameters, no required fields, and an output schema exists, the description provides a good overview of purpose and usage but lacks behavioral transparency. It covers return values properly and distinguishes from sibling, but could add more on prerequisites and side effects.

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%, so baseline is 3. Description adds high-level context (e.g., 'You provide the lyrics with section markers') but mostly paraphrases the schema's parameter descriptions without adding significant new meaning.

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 it generates AI music with full control over lyrics, title, and style (Custom Mode). It distinguishes itself from sibling tool suno_generate_music by specifying that this tool is for custom lyrics vs quick generation.

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 when-to-use: specific lyrics, precise style control, need title, vocal gender, auto-generate from prompt. Also gives clear alternative: use suno_generate_music for quick generation without writing lyrics.

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