Skip to main content
Glama
AceDataCloud

SunoMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

suno_generate_with_persona_vox

Generate music with a saved vocal persona for strict voice consistency. Use for multiple songs needing identical vocal style, applying the persona's voice to new prompts.

Instructions

Generate music using a saved artist persona with VOX-specific consistency.

Similar to suno_generate_with_persona but uses the artist_consistency_vox action,
which is optimized for vocal consistency with a persona.

Use this when:
- You want multiple songs with the same vocal style using VOX mode
- You need stricter vocal consistency than suno_generate_with_persona provides
- You're creating content with a specific voice persona

First create a persona with suno_create_persona or suno_create_voice, then use its ID here.

Returns:
    Task ID and generated audio information with the persona's voice applied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoModel version to use.chirp-v5-5
promptYesDescription of the music to generate. The persona's voice will be applied to this new song.
audio_idYesID of a reference audio to base the generation on.
persona_idYesID of the persona to use for the VOX generation. Get this from suno_create_persona or suno_create_voice tool.
callback_urlNoWebhook callback URL for asynchronous notifications.

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. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden. It discloses the underlying action (artist_consistency_vox), its optimization for vocal consistency, that it is stricter than the sibling, and that it returns a Task ID and generated audio information. This gives the agent a solid understanding of behavior and expected output.

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 well-structured with a front-loaded purpose, clear bullet points for usage, and a brief returns note. 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.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, an output schema, and no annotations, the description covers purpose, usage conditions, prerequisites, and return type comprehensively. It provides everything an agent needs to decide when to call it and what to expect.

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 coverage is 100%, so the schema already documents every parameter. The description adds value by explaining the persona_id prerequisite (create persona via suno_create_persona or suno_create_voice) and by implying the vocal consistency context, but it does not add meaning to audio_id, model, or callback_url beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's verb ('Generate music'), resource ('saved artist persona with VOX-specific consistency'), and explicitly differentiates it from the sibling suno_generate_with_persona by mentioning the artist_consistency_vox action and stricter vocal consistency. This is specific and unambiguous.

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 explicit 'Use this when' bullets listing concrete conditions (multiple songs, stricter vocal consistency, specific voice persona), names the alternative (suno_generate_with_persona), and gives a prerequisite (create persona first). This is thorough guidance that leaves no ambiguity about when to select this tool.

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

Deploy Server

Other Tools