Skip to main content
Glama
runapi-ai

suno-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_persona

Create a Suno music persona from a reference audio clip using source task and audio IDs. Provide a persona name and description to define the new voice profile.

Instructions

Run a synchronous Suno operation on RunAPI (generate persona). Returns the operation result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPersona name.
descriptionYesPersona description.
source_task_idYesRunAPI Task id that produced the reference audio.
source_audio_idYesAudio id within the source Task that carries the reference vocals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.3.6
    • removedInput schema / properties / audio_id
      Removed value: -{
-  "description": "Audio ID within the source task.",
-  "type": "string"
-}
    • addedInput schema / properties / source_audio_id
      Added value: +{
+  "description": "Audio id within the source Task that carries the reference vocals.",
+  "type": "string"
+}
    • addedInput schema / properties / source_task_id
      Added value: +{
+  "description": "RunAPI Task id that produced the reference audio.",
+  "type": "string"
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "Source task ID with reference vocals.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id",
-  "audio_id",
-  "name",
-  "description"
-]New value: +[
+  "source_task_id",
+  "source_audio_id",
+  "name",
+  "description"
+]
  2. Addedv0.3.5

TDQS

B3.1/5.0
Behavior3/5

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

The description discloses that the operation is synchronous and returns the result, which is useful behavioral context. However, with no annotations, it fails to mention potential side effects (e.g., creating a persona, consuming credits), authentication requirements, or error behavior. It is minimal but not misleading.

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 a single, focused sentence that front-loads the main action and result. It is free of fluff and every word earns its place, though it could incorporate additional useful context without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, an output schema, and the tool's four required parameters, the description is notably incomplete. It does not explain what a persona is, what the returned result looks like, or any preconditions on the source task and audio IDs. An agent would have to infer these from the schema alone.

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?

All parameters are fully described in the schema (100% coverage), so the baseline is 3. The description itself does not add any semantic nuance beyond the schema, such as how parameters interrelate or what the source task/audio IDs represent in the operation flow.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Run a synchronous Suno operation') and identifies the specific operation ('generate persona'), which matches the tool name. It is not a tautology because it adds the 'synchronous' and 'RunAPI' context, but it does not explain what a persona is or how this differs from sibling tools like generate_voice.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as generate_voice or text_to_music. The description provides no context about prerequisites, intended scenarios, or conditions that would make this tool the right choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools