Skip to main content
Glama

producer_generate_music

Generate AI music from a text prompt, automatically creating lyrics, melody, style, and arrangement for quick songs with minimal input.

Instructions

Generate AI music from a text prompt using Producer/Riffusion.

This is the simplest way to create music - just describe what you want and
Producer 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 the AI to be creative with the arrangement

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

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "producer_generate_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoSeed for reproducible generation. Reuse the same seed to reproduce a result.
asyncNoWhether to process the request asynchronously.
modelNoProducer model version. 'FUZZ-2.0' is the default and recommended for most use cases. 'FUZZ-2.0 Pro' offers the highest quality. 'FUZZ-2.0 Raw' provides raw unprocessed output.FUZZ-2.0
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'
weirdnessNoCreative control for how experimental/unusual the generation is. Range 0-1.
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API will call this URL when the audio is generated.
instrumentalNoIf true, generate instrumental music without vocals. Default is false (with vocals).
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. Changed2 schema fields changedv0.1.23
    • 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."
  2. 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"
      +  }
      +]
  3. 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"
      +}
  4. Addedv0.1.13
  5. Removedv0.1.12
  6. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses that lyrics, melody, style, and arrangement are auto-generated and what is returned, but never explains the async/callback_url flow, generation latency or cost, or any rate limits — meaningful gaps for a 9-parameter generation call.

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?

Front-loaded purpose sentence, then scannable bullets, then a returns note — nothing is wasted. The 'simplest way' editorializing sentence is slightly redundant with the usage bullets but earns its place as framing.

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 explain return fields (it does anyway), and the 100%-covered input schema handles parameters. The remaining gap is the async/callback behavior, which is the one thing an agent could get wrong given no annotations.

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 parameter (seed, model, weirdness, instrumental, strengths, async, callback_url) is already documented in the schema. The description adds only an indirect hint that lyrics and style are controllable elsewhere; baseline 3 applies when the schema does the work.

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?

States a specific verb and resource ('Generate AI music from a text prompt') and pinpoints the provider (Producer/Riffusion). It also distinguishes itself from the closest sibling by naming producer_generate_custom_music as the full-control alternative.

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?

Explicit 'Use this when' bullets cover the three selecting conditions (minimal input, no lyrics in mind, let AI handle arrangement). The alternative is named with the exact condition that should route an agent elsewhere.

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