Skip to main content
Glama

producer_generate_custom_music

Generate AI music from your own structured lyrics, title, and style prompt, with control over melody and arrangement for custom song creation.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "producer_generate_custom_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for reproducible generation. Reuse the same seed to reproduce a result.
asyncNoWhether to process the request asynchronously.
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
modelNoProducer model version. 'FUZZ-2.0' or 'FUZZ-2.0 Pro' recommended for best quality.FUZZ-2.0
titleNoOptional title of the song. Keep it concise and memorable.
promptNoMusic style prompt. 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'
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.2-1.
lyrics_strengthNoCreative control for how strongly the lyrics drive the generation. Range 0-1.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.23
    • addedInput schema / properties / lyric / default
      Added value: +""
    • changedInput schema / properties / sound_strength / anyOf
      Previous value: -[
      -  {
      -    "maximum": 1,
      -    "minimum": 0,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 1,
      +    "minimum": 0.2,
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sound_strength / description
      Previous value: -"Creative control for how strongly the sound/style drives the generation. Range 0-1."New value: +"Creative control for how strongly the sound/style drives the generation. Range 0.2-1."
    • addedInput schema / properties / title / default
      Added value: +""
    • changedInput schema / properties / title / description
      Previous value: -"Title of the song. Keep it concise and memorable."New value: +"Optional title of the song. Keep it concise and memorable."
    • removedInput schema / required
      Removed value: -[
      -  "lyric",
      -  "title"
      -]
  2. Changed2 schema fields changedv0.1.18
    • addedInput schema / properties / prompt
      Added value: +{
      +  "default": "",
      +  "description": "Music style prompt. 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'",
      +  "title": "Prompt",
      +  "type": "string"
      +}
    • removedInput schema / properties / style
      Removed value: -{
      -  "default": "",
      -  "description": "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'",
      -  "title": "Style",
      -  "type": "string"
      -}
  3. Changed2 schema fields changedv0.1.16
    • addedInput schema / properties / async
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Whether to process the request asynchronously.",
      +  "title": "Async"
      +}
    • changedInput schema / properties / seed / anyOf
      Previous value: -[
      -  {
      -    "type": "integer"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  4. Changed4 schema fields changedv0.1.15
    • addedInput schema / properties / lyrics_strength
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1,
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Creative control for how strongly the lyrics drive the generation. Range 0-1.",
      +  "title": "Lyrics Strength"
      +}
    • addedInput schema / properties / seed
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Seed for reproducible generation. Reuse the same seed to reproduce a result.",
      +  "title": "Seed"
      +}
    • addedInput schema / properties / sound_strength
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1,
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Creative control for how strongly the sound/style drives the generation. Range 0-1.",
      +  "title": "Sound Strength"
      +}
    • addedInput schema / properties / weirdness
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 1,
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Creative control for how experimental/unusual the generation is. Range 0-1.",
      +  "title": "Weirdness"
      +}
  5. Addedv0.1.13
  6. Removedv0.1.12
  7. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does state the return shape (task ID plus audio URLs, title, lyrics, duration), which signals task-based/asynchronous behavior, but it omits cost/credit implications, generation latency, and polling expectations for a long-running generation call. Also, 'You provide the lyrics' implies lyrics are mandatory while the schema's instrumental flag makes them optional and ignored.

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?

Front-loaded purpose sentence, then a short explanatory line, a bulleted when-to-use block, an explicit alternative, and a Returns block. Structure is scannable and no sentence is filler.

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?

With an output schema present, the description needn't enumerate return fields in depth, and it does summarize them. For an 11-parameter generation tool with zero annotations, it could do more on async/task lifecycle and on the fact that all parameters are optional with defaults, but it is largely sufficient to call correctly.

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 every one of the 11 parameters is already documented in the schema, including section markers, model enum, and the strength knobs. The description only restates that lyrics carry section markers and that title/style are controllable, adding little beyond the schema; baseline 3 applies.

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?

A specific verb ('Generate') plus resource ('AI music') with the differentiator front-loaded: 'full control over lyrics, title, and style.' It explicitly names the sibling producer_generate_music as the lighter-weight alternative, so an agent can route between them without opening schemas.

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 an explicit 'Use this when' list (own lyrics, precise style control, specific title) and a named alternative with its selection condition ('For quick generation without writing lyrics, use producer_generate_music instead'). Both sides of the routing decision are covered.

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