Skip to main content
Glama

suno_generate_with_persona_vox

Generate new songs with a saved persona's voice using VOX mode for strict vocal consistency. Ideal for creating multiple tracks with the same vocal style.

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?

No annotations are provided, so the description must carry the full burden. It explains the tool uses a VOX action for vocal consistency and returns Task ID and audio info. While it doesn't cover auth or rate limits, the behavioral description is adequate for a generation tool.

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 clear sections: main action, similarity, usage conditions, prerequisite, and returns. Every sentence is necessary and front-loaded with the core purpose.

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?

Given the tool has 5 parameters and an output schema, the description covers the key aspects: action, when to use, prerequisite, and return type. It could mention any limitations or queuing behavior, but is largely complete.

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%, so baseline is 3. The description adds value by explaining how persona_id relates to other tools and that the prompt's voice will be applied, going beyond the schema descriptions.

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 generates music using a saved artist persona with VOX-specific consistency, and explicitly distinguishes it from the sibling suno_generate_with_persona by noting it uses the artist_consistency_vox action.

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 usage conditions in a 'Use this when:' list, including three specific scenarios and a prerequisite (create persona first). This gives clear when-to-use and when-not-to-use guidance.

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