Skip to main content
Glama

suno_create_voice

Create a custom voice persona from an external audio URL containing clear vocals. Returns a Persona ID for use in song generation.

Instructions

Create a custom voice persona from an external audio URL.

Creates a voice persona directly from a publicly accessible audio URL
(MP3 or WAV format). The audio must contain clear vocals from a single
speaker and be at least 10 seconds long.

This is different from suno_create_persona which creates a persona from
a previously generated Suno audio. Use this to create a persona from
your own voice recordings or external audio files.

Use this when:
- You have an external audio file with clear vocals
- You want to create a voice persona from your own recordings
- You want to use a specific real-world voice as a persona

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesPublicly accessible URL of the audio file to create a voice from. Must be MP3 or WAV format, at least 10 seconds long, containing clear vocals from a single speaker without background noise or music.
nameYesName for the custom voice persona.
descriptionNoDescription of the custom voice persona (optional).

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 carries the full burden. It discloses input constraints (public URL, MP3/WAV, clear vocals, single speaker, at least 10 seconds) and states the output (Persona ID). However, it does not detail error handling, idempotency, or side effects like persistence, which would improve transparency.

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 bullet points and clear sections, front-loading key information. Every sentence is informative and necessary, with no redundancy or wasted words. It is appropriately sized for the tool's complexity.

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 moderate complexity (3 parameters, output schema exists but not detailed), the description covers input constraints, usage scenarios, and output. It is complete enough for an AI agent to invoke correctly, though missing potential error states or rate limits would further enhance completeness.

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?

The input schema has 100% coverage with descriptions for all three parameters. The tool description adds value by reinforcing the audio URL requirements (publicly accessible, format, content quality) and clarifying the name and optional description purpose. This goes beyond the schema's basic 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's purpose: creating a custom voice persona from an external audio URL. It uses specific verbs ('create') and resource ('custom voice persona') and differentiates from the sibling tool suno_create_persona by contrasting input sources (external URL vs. previously generated Suno audio).

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 guidance on when to use this tool: when the user has an external audio file, wants to create a persona from own recordings, or wants to use a specific real-world voice. It also explicitly contrasts with suno_create_persona, helping the agent choose the correct tool.

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