Skip to main content
Glama

suno_generate_with_persona_vox

Generate music with consistent vocal style using a saved artist persona in VOX mode. Apply the persona's voice to a new song prompt with optional audio reference.

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
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.
promptYesDescription of the music to generate. The persona's voice will be applied to this new song.
modelNoModel version to use.chirp-v5-5
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description clearly states the return type (Task ID and generated audio information), but does not elaborate on the audio info's content or any other behavioral traits like rate limits. Still, it adequately describes the tool's behavior.

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?

Well-structured: brief intro, comparison to sibling, bullet-point usage guidelines, prerequisite, and return statement. No unnecessary sentences.

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?

Provides usage context and distinguishes from sibling, but could elaborate on output structure (beyond 'generated audio information'). Schema and output schema exist but not described in detail. Adequate for a generation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, yet description adds value by clarifying the purpose of each parameter: audio_id as reference audio, persona_id sourced from specific tools, prompt as description with voice applied, model version list, and callback_url for webhook.

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?

Description clearly states it generates music using a saved artist persona with VOX-specific consistency, and explicitly distinguishes from sibling suno_generate_with_persona by highlighting the use of artist_consistency_vox action for stricter vocal consistency.

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 when-to-use scenarios: multiple songs with same vocal style, stricter consistency, specific voice persona. Also includes prerequisite instruction to first create a persona via suno_create_persona or suno_create_voice.

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

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