Skip to main content
Glama

suno_create_persona

Save vocal characteristics from a generated song to create a reusable voice style for consistent vocals across multiple songs.

Instructions

Create a new artist persona from an existing audio's vocal style.

This saves the vocal characteristics from a generated song so you can reuse
that same voice style in future generations. Great for maintaining consistency
across multiple songs.

Use this when:
- You generated a song and love the voice
- You want to create multiple songs with the same vocalist
- You're building an album with consistent vocal style
- You want to save a unique voice for future use

After creating a persona, use suno_generate_with_persona with the returned
persona_id to generate new songs with that voice.

Returns:
    Persona ID that can be used with suno_generate_with_persona tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_idYesID of the audio to use as the persona reference. This should be a previously generated song whose vocal style you want to save and reuse.
nameYesName for this persona. Use a descriptive name that helps you remember the voice style. Examples: 'My Rock Voice', 'Soft Female Singer', 'Deep Male Baritone', 'Energetic Pop Vocalist'
vox_audio_idNoOptional audio ID used to generate a new singer's style by combining with the main audio. Useful for creating hybrid vocal personas.
vocal_startNoStart time in seconds of the vocal segment to use from the audio. Useful for isolating a specific vocal section.
vocal_endNoEnd time in seconds of the vocal segment to use from the audio.
descriptionNoDescription of the singer's style. Examples: 'Warm and breathy female voice with jazz influences', 'Powerful male rock vocalist with raspy tone'

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 carries the full burden. It clearly states that the tool saves vocal characteristics and returns a persona_id. It does not mention prerequisites (e.g., needing a generated audio_id) or error conditions, but overall the behavioral traits are well communicated.

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 clear opening statement, bullet points for use cases, and a follow-up action note. Every sentence serves a purpose and there is no fluff. It is front-loaded with the main action.

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's complexity (6 parameters, 2 required, output schema exists), the description covers the purpose, use cases, and output (persona_id). It does not detail the output schema but mentions the return value. It could mention input prerequisites or error handling, but overall it is fairly complete.

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 the baseline is 3. The tool description adds context about the workflow but does not enhance parameter semantics beyond what the schema already provides. The schema descriptions are already detailed.

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 purpose: extracting vocal characteristics from an existing audio to create a reusable persona. It distinguishes from siblings by explicitly mentioning the subsequent use with suno_generate_with_persona and differentiating it from other creation tools like suno_create_voice.

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 provides explicit 'Use this when' bullet points listing four specific scenarios (loved voice, multiple songs, album consistency, unique voice). It also tells the user what to do after creating a persona, effectively guiding the workflow.

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