Skip to main content
Glama

producer_generate_custom_music

Generate custom AI music by providing your own lyrics, title, and style. Control the musical output precisely for your needs.

Instructions

Generate AI music with full control over lyrics, title, and style.

This gives you complete creative control over the song. You provide the lyrics
with section markers, and Producer 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

For quick generation without writing lyrics, use producer_generate_music instead.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoSeed for reproducible generation. Reuse the same seed to reproduce a result.
asyncNoWhether to process the request asynchronously.
lyricYesSong 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
modelNoProducer model version. 'FUZZ-2.0' or 'FUZZ-2.0 Pro' recommended for best quality.FUZZ-2.0
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'
titleYesTitle of the song. Keep it concise and memorable.
weirdnessNoCreative control for how experimental/unusual the generation is. Range 0-1.
callback_urlNoWebhook callback URL for asynchronous notifications.
instrumentalNoIf true, generate instrumental version (lyrics will be ignored). Default is false.
sound_strengthNoCreative control for how strongly the sound/style drives the generation. Range 0-1.
lyrics_strengthNoCreative control for how strongly the lyrics drive the generation. Range 0-1.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations exist, so the description carries full weight. It discloses the main workflow (user provides lyrics, Producer generates melody/arrangement) and mentions return content (Task ID and audio info). However, it does not clarify async behavior or how to retrieve results via task ID, and the phrase 'Returns Task ID and generated audio information' is ambiguous for asynchronous requests.

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 concise, front-loaded with purpose, uses bullet points for usage, includes an alternative, and ends with a clear Returns section. Every sentence earns its place without redundancy.

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?

The description covers core purpose, usage guidance, alternatives, and return values. While it lacks explicit mention of async result retrieval, the output schema and sibling get_task tool cover that gap, making it sufficiently complete for a tool with 11 parameters.

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% with detailed parameter descriptions (e.g., lyric markers, style examples). The description adds focus on lyrics, title, and style but no new semantic information beyond the schema, meeting the baseline.

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 begins with 'Generate AI music with full control over lyrics, title, and style,' providing a specific verb and resource. It explicitly distinguishes from the sibling tool: 'For quick generation without writing lyrics, use producer_generate_music instead.'

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?

Clear bullet-list of when to use (specific lyrics, precise control, specific title) and explicit alternative (producer_generate_music) with rationale. This is exactly the kind of guidance needed for tool selection.

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/ProducerMCP'

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