Skip to main content
Glama
runapi-ai

suno-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

generate_persona

Generate a Suno persona from reference audio using source task/audio IDs, name, and description. Returns the operation result.

Instructions

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.4.0
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / description / description
      Previous value: -"Persona description."New value: +"Persona description. Declared type: string."
    • changedInput schema / properties / name / description
      Previous value: -"Persona name."New value: +"Persona name. Declared type: string."
    • changedInput schema / properties / source_audio_id / description
      Previous value: -"Audio id within the source Task that carries the reference vocals."New value: +"Audio id within the source Task that carries the reference vocals. Declared type: string."
    • changedInput schema / properties / source_task_id / description
      Previous value: -"RunAPI Task id that produced the reference audio."New value: +"RunAPI Task id that produced the reference audio. Declared type: string."
  2. 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"
+]
  3. Addedv0.3.5

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the operation is synchronous and returns a result, but omits whether it consumes credits, requires authentication, creates persistent resources, or has other side effects.

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 two short sentences with no wasted words. It is front-loaded with the operation type, though it omits useful context that would make it more actionable.

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?

For a generation tool with four required parameters, no annotations, and no output schema, the description is too sparse. It does not explain what the operation returns beyond 'operation result', when to choose it over siblings, or what a persona represents, leaving significant gaps for an agent.

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?

The input schema has 100% description coverage, fully documenting all four required parameters (source_task_id, source_audio_id, name, description). The description adds no parameter details beyond what the schema already provides, so the baseline of 3 is appropriate.

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

Purpose3/5

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

The description states a general verb and resource ('Run a synchronous Suno operation') and names the operation in parentheses, but the parenthetical merely restates the tool name. It does not explain what a 'persona' is, how it differs from siblings like generate_voice or inspire_music, or what source audio produces it.

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?

No guidance is given on when to use this tool versus alternatives such as generate_voice, cover_audio, or text_to_music. The description provides no prerequisites, context, or exclusions, leaving usage entirely to inference.

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