Skip to main content
Glama
AceDataCloud

SunoMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

suno_generate_music

Describe the music you want, and get a full AI-generated song with lyrics, melody, and arrangement automatically. Just provide a genre, mood, or theme.

Instructions

Generate AI music from a text prompt using Suno's Inspiration Mode.

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

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoSuno model version. 'chirp-v5-5' is the latest and recommended for best quality with 8-minute max duration. 'chirp-v4-5' is a reliable choice for most use cases. Older models (v3, v3-5, v4) have shorter duration limits.chirp-v5-5
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'
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).
variation_categoryNoVariation intensity for v5+ models. 'high' for maximum variation, 'normal' for balanced, 'subtle' for minimal changes. Only supported in chirp-v5 and above.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.18
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "chirp-v3-0",
-  "chirp-v3-5",
-  "chirp-v4",
-  "chirp-v4-5",
-  "chirp-v4-5-plus",
-  "chirp-v5",
-  "chirp-v5-5"
-]New value: +[
+  "chirp-v6",
+  "chirp-v6-wild",
+  "chirp-v6-mini",
+  "chirp-v3-0",
+  "chirp-v3-5",
+  "chirp-v4",
+  "chirp-v4-5",
+  "chirp-v4-5-plus",
+  "chirp-v5",
+  "chirp-v5-5"
+]
  2. Addedv0.1.5
  3. Removedv0.1.3
  4. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / variation_category
      Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "high",
+        "normal",
+        "subtle"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Variation intensity for v5+ models. 'high' for maximum variation, 'normal' for balanced, 'subtle' for minimal changes. Only supported in chirp-v5 and above.",
+  "title": "Variation Category"
+}
  5. 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 provided, so the description carries the burden for behavioral disclosure. It does explain that Suno auto-generates lyrics, style, and arrangement, and lists a Task ID plus audio URLs, title, lyrics, and duration as return values. However, it doesn't explicitly say whether generation is asynchronous or how the returned Task ID should be used to track the result, which is relevant for a generation API.

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?

The description is front-loaded with a clear one-line purpose, followed by compact use-case guidance, a sibling alternative, and a Returns summary. It is longer than the minimal necessary, but each section earns its place and no content is redundant with the schema.

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?

For a 5-param tool with 100% schema coverage and an output schema present, the description is largely complete: it explains what to expect, when to use it, and when to switch to the custom generation tool. The main gap is the lack of explicit async/task-lifecycle guidance, but the mention of Task ID and the presence of structured schema/output info make this adequate rather than deficient.

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%, and the schema already documents prompt, model, callback_url, instrumental, and variation_category with meaningful details. The description adds high-level context around the prompt and the automatic-generation behavior, but it doesn't enrich the semantics of individual parameters beyond what the schema provides.

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 opens with a specific verb and resource: 'Generate AI music from a text prompt using Suno's Inspiration Mode.' It clarifies what the tool does and distinguishes it from suno_generate_custom_music by emphasizing automatic lyrics, melody, style, and arrangement.

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?

The description gives explicit when-to-use conditions: 'quick music generation with minimal input,' 'no specific lyrics in mind,' and 'want Suno to be creative.' It also names the alternative, suno_generate_custom_music, and states when to choose it instead.

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