Skip to main content
Glama

suno_generate_with_persona

Apply a saved persona to generate new songs with consistent vocal style. Create multiple tracks with the same voice by providing a persona ID and music description.

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 provided, so description must carry full burden. It discloses that the tool generates new music with persona voice and returns a task ID, but does not state mutation, idempotency, or synchronicity details. Adequate but not rich.

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?

Description is efficient with 9 sentences including a bullet list. No fluff, though 'Returns' line is slightly redundant given output schema existence.

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 output schema exists, description adequately covers the main flow, requires steps (create persona first), and differentiates from siblings. Could optionally mention optional parameters like 'model' or 'callback_url'.

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 baseline 3. Description restates parameter purposes but adds no new semantics beyond schema. For example, 'prompt' is described similarly in both.

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 'Generate music using a saved artist persona for consistent vocal style', specifying the verb (generate), resource (music with persona), and distinguishes from siblings like suno_generate_music (no persona) and suno_create_persona (creates persona).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use this when' bullets list three specific scenarios (multiple songs with same style, album/series, reusing favorite voice) and mentions prerequisite to create persona first. Lacks explicit when-not-to-use or alternatives like suno_generate_music, but positive guidance is strong.

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