Skip to main content
Glama

suno_generate_with_persona

Generate new songs with a consistent vocal style by applying a saved artist persona to music prompts.

Instructions

Generate music using a saved artist persona for consistent vocal style.

This allows you to maintain a consistent voice/singing style across multiple
songs by using a previously saved persona.

Use this when:
- You want multiple songs with the same vocal style
- You're creating an album or series with consistent vocals
- You found a voice you like and want to reuse it

First create a persona with suno_create_persona, 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. Get this from suno_create_persona tool. The persona defines the vocal style and characteristics.
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. When provided, the API will call this URL when the audio is generated.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions the return value (Task ID and generated audio information) but does not disclose other behavioral traits such as whether the operation is synchronous or asynchronous, rate limits, or if it has any side effects. The callback_url parameter suggests async support, but the description does not elaborate.

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 well-structured with a clear opening sentence and bullet-style use cases. It is not overly verbose but could be slightly more concise. However, it effectively communicates the key points without unnecessary detail.

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 the presence of an output schema, the description appropriately mentions the return value. All parameters are covered by the schema, and the description explains the tool's niche relative to sibling tools. The context is complete for an agent to understand when and how to use this tool.

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 schema already documents all parameters. The description adds some context (e.g., 'use its ID here' for persona_id) but does not significantly enhance understanding beyond what is in the schema. Baseline for high coverage is 3.

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: to generate music using a saved persona for consistent vocal style. It distinguishes from sibling tools like suno_generate_music by emphasizing persona reuse, and mentions the prerequisite of using suno_create_persona.

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 explicitly lists when to use this tool (multiple songs with same style, album/series, reusing a voice) and provides a clear prerequisite: create a persona first with suno_create_persona. This gives definitive guidance on when this tool is appropriate and how to prepare.

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