Skip to main content
Glama
runapi-ai

suno-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task

Retrieve the current status and latest result payload for an asynchronous Suno task using its task ID and action endpoint.

Instructions

Fetch the current status and latest result payload for a suno task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAsynchronous endpoint the task was created on.
task_idYesTask id returned when the task was created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.3.6
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "add_samples",
-  "blend_lyrics",
-  "cover_audio",
-  "create_mashup",
-  "extend_music",
-  "generate_lyrics",
-  "inspire_music",
-  "remaster_audio",
-  "separate_audio_stems",
-  "stitch_audio",
-  "text_to_music",
-  "text_to_sound"
-]New value: +[
+  "convert_audio",
+  "blend_lyrics",
+  "cover_audio",
+  "create_mashup",
+  "extend_music",
+  "generate_lyrics",
+  "inspire_music",
+  "add_samples",
+  "visualize_music",
+  "remaster_audio",
+  "separate_audio_stems",
+  "stitch_audio",
+  "text_to_music",
+  "text_to_sound"
+]
  3. Changed1 schema field changedv0.3.2
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "blend_lyrics",
-  "cover_audio",
-  "create_mashup",
-  "extend_music",
-  "generate_lyrics",
-  "separate_audio_stems",
-  "text_to_music",
-  "text_to_sound"
-]New value: +[
+  "add_samples",
+  "blend_lyrics",
+  "cover_audio",
+  "create_mashup",
+  "extend_music",
+  "generate_lyrics",
+  "inspire_music",
+  "remaster_audio",
+  "separate_audio_stems",
+  "stitch_audio",
+  "text_to_music",
+  "text_to_sound"
+]
  4. Changed2 schema fields changedv0.2.4
    • changedInput schema / properties / action / description
      Previous value: -"Endpoint the task was created on."New value: +"Asynchronous endpoint the task was created on."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "cover_audio",
-  "create_mashup",
-  "extend_music",
-  "generate_lyrics",
-  "text_to_music",
-  "text_to_sound"
-]New value: +[
+  "blend_lyrics",
+  "cover_audio",
+  "create_mashup",
+  "extend_music",
+  "generate_lyrics",
+  "separate_audio_stems",
+  "text_to_music",
+  "text_to_sound"
+]
  5. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "cover_audio",
-  "create_mashup",
-  "extend_music",
-  "text_to_music",
-  "text_to_sound"
-]New value: +[
+  "cover_audio",
+  "create_mashup",
+  "extend_music",
+  "generate_lyrics",
+  "text_to_music",
+  "text_to_sound"
+]
  6. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool is a read-like fetch returning status and the latest result payload, but it omits authentication requirements, rate limits, error behavior, and whether the task may still be processing.

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 a single, well-structured sentence that front-loads the action and resource. Every word earns its place with no filler or redundancy.

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

Completeness3/5

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

For a two-parameter retrieval tool with no output schema, the description mentions what is returned ('status and latest result payload') but does not explain the shape or meaning of that payload, nor does it cover polling or error semantics. It is minimally adequate but leaves notable gaps.

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 both task_id and action. The description adds no parameter-level detail beyond the phrase 'suno task', making the baseline score of 3 appropriate.

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 states a specific verb ('Fetch') and resource ('current status and latest result payload for a suno task'), making the tool's purpose clear. It distinguishes itself from the action-creation siblings like convert_audio and text_to_music, though it does not explicitly name an alternative.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not explain that this tool should be called after creating an asynchronous task with one of the action endpoints, nor does it mention polling frequency or failure conditions.

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