SunoMCP

suno_generate_custom_music

Create original AI songs using custom lyrics with [Verse] and [Chorus] markers. Define titles, musical styles, and vocal settings to generate personalized tracks with precise control.

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)

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

Name	Required	Description	Default
`lyric`	Yes	Song 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
`title`	Yes	Title of the song. Keep it concise and memorable.
`style`	No	Music 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'
`model`	No	Suno model version. 'chirp-v5-5' or 'chirp-v5' recommended for best quality.	chirp-v5-5
`instrumental`	No	If true, generate instrumental version (lyrics will be ignored). Default is false.
`style_negative`	No	Styles to explicitly exclude from the generation. Examples: 'heavy metal, screaming', 'autotune, electronic'
`vocal_gender`	No	Preferred vocal gender. 'f' for female, 'm' for male, empty string for AI to decide. Only works with v4.5+ models.
`callback_url`	No	Webhook callback URL for asynchronous notifications. When provided, the API will call this URL when the audio is generated.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Tool Definition Quality

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the creative workflow (user provides lyrics with section markers, Suno generates melody/arrangement), the async nature (returns Task ID), and model version constraints (v4.5+ for vocal gender). Could improve by mentioning potential generation failures or task 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear visual hierarchy: summary, detailed explanation, bullet-point usage criteria, alternative recommendation, and returns. Front-loaded with key differentiator ('Custom Mode'). Minor deduction for the 'Returns' section which is redundant given the output schema exists.

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 high schema coverage (100%), output schema presence, and 20+ sibling tools, the description adequately situates the tool within the ecosystem (custom vs. quick generation). It covers the required prerequisites (lyrics structure) and references the async Task ID return. Could explicitly state that generation is asynchronous and requires task polling.

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 mentions lyrics, title, style, and vocal gender in the text, but adds no semantic information beyond what the comprehensive schema already provides (e.g., section marker examples, enum values, defaults are all in schema).

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?

Opens with specific verb ('Generate') + resource ('AI music') + scope ('full control', 'Custom Mode'). The parenthetical '(Custom Mode)' and reference to the sibling tool clearly distinguish it from suno_generate_music.

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?

Contains explicit 'Use this when:' section with four specific scenarios (specific lyrics, precise style control, specific title, vocal gender). Explicitly names the alternative: 'For quick generation without writing lyrics, use suno_generate_music instead.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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