Skip to main content
Glama
runapi-ai

suno-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

convert_audio

Submit a source audio ID to create a Suno conversion task on RunAPI; get the task ID, status, and output URLs.

Instructions

Create a Suno task on RunAPI (convert audio). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
timeout_msNo
callback_urlNoWebhook URL for async notifications. Declared type: string.
source_task_idNoRunAPI Task id that produced the audio. Required when the audio id alone does not identify the source. Declared type: string.
source_audio_idYesAudio id within the source Task, or a RunAPI audio resource id returned by a previous request. Declared type: string.
poll_interval_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for async notifications."New value: +"Webhook URL for async notifications. Declared type: string."
    • changedInput schema / properties / source_audio_id / description
      Previous value: -"Audio id within the source Task, or a RunAPI audio resource id returned by a previous request."New value: +"Audio id within the source Task, or a RunAPI audio resource id returned by a previous request. Declared type: string."
    • changedInput schema / properties / source_task_id / description
      Previous value: -"RunAPI Task id that produced the audio. Required when the audio id alone does not identify the source."New value: +"RunAPI Task id that produced the audio. Required when the audio id alone does not identify the source. Declared type: string."
  2. Addedv0.3.6

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return shape (task id, status, output URLs) but does not state whether this is async, what permissions/credits are needed, what 'convert' actually does to the audio, or how failures surface. This is a significant gap for a task-creation/mutation tool.

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?

Two short sentences, front-loaded with the action, and no wasted wording. It earns its length but is under-specified rather than overly verbose.

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 6-parameter task-creation tool with no annotations and no output schema, the description is too thin. It should clarify what conversion does, the async/polling contract, and distinguish itself from sibling audio transforms; the return-shape sentence is the only substantive content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description mentions none of the 6 parameters. Schema coverage is 67%, so the schema documents most inputs (wait, callback_url, source_task_id, source_audio_id), but roughly a third are undocumented and the description compensates for nothing. It adds no meaning beyond the schema.

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?

It states a verb ('Create') and a resource ('Suno task on RunAPI') plus a parenthetical 'convert audio'. However, 'convert' is left undefined against siblings like cover_audio, remaster_audio, and separate_audio_stems, so an agent cannot tell what transformation this performs. The purpose is identifiable but genuinely vague.

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 on when to use this versus the many sibling audio tools (cover_audio, remaster_audio, separate_audio_stems, extend_music). No prerequisites or exclusions are stated. The agent must infer usage from the name alone.

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