Skip to main content
Glama

Split, clean up or enhance audio (no account needed)

create_free_audio_job

Split stems, isolate vocals, split lead from backing vocals, remove noise or reverb, or enhance a vocal. No account, API key or sign-up needed: one free use of each tool per network, of a file up to five minutes, as on the website. A connected account runs it on that account's plan instead. Returns an upload URL; PUT the file, then use get_free_audio_job.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool": "<tool>"
    },
    "name": "create_free_audio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYessplit_stems: vocals and instrumental. split_lead_backing: lead vocal, backing vocals, instrumental, and the instrumental with backing vocals. remove_noise: background noise out of a voice recording. remove_reverb: room echo and reverb out of a voice recording. enhance_vocal: a clearer phone-recorded or noisy vocal, keeping the singer's voice.
audioNoThe audio file the user attached. NiceVois downloads and uploads it itself, so no upload step is needed.
fileNameNoWithout an attached file: the audio file's name with its extension: WAV, MP3, FLAC, M4A or OGG.
sizeBytesNoWithout an attached file: the file's exact size in bytes.
outputFormatNoFormat of the files you get back. Use wav unless the user asks for another.wav
durationSecondsNoThe audio's length in seconds, if you can measure it. NiceVois measures the file itself after upload, so leave this out rather than guess.

Output Schema

NameRequiredDescriptionDefault
idYes
toolYes
errorNo
linksYes
priceNo
stageNo
statusYes
uploadYes
messageNo
outputsYes
fileNameNo
toolNameYes
createdAtNo
websiteUrlYes
durationSecondsNo
pollAfterSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • removedOutput schema / properties / createdAt / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / createdAt / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / durationSeconds / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / durationSeconds / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / error / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / error / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / fileName / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / fileName / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / message / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / message / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / stage / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / stage / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. Changed4 schema fields changed
    • addedInput schema / properties / audio
      Added value: +{
      +  "description": "The audio file the user attached. NiceVois downloads and uploads it itself, so no upload step is needed.",
      +  "properties": {
      +    "download_url": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / fileName / description
      Previous value: -"The audio file's name with its extension: WAV, MP3, FLAC, M4A or OGG."New value: +"Without an attached file: the audio file's name with its extension: WAV, MP3, FLAC, M4A or OGG."
    • changedInput schema / properties / sizeBytes / description
      Previous value: -"The file's exact size in bytes."New value: +"Without an attached file: the file's exact size in bytes."
    • changedInput schema / required
      Previous value: -[
      -  "tool",
      -  "fileName",
      -  "sizeBytes"
      -]New value: +[
      +  "tool"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / tool / description
      Previous value: -"split_stems: vocals and instrumental. split_lead_backing: lead vocal, backing vocals, instrumental, and the instrumental with backing vocals. remove_noise: background noise out of a voice recording. remove_reverb: room echo and reverb out of a voice recording."New value: +"split_stems: vocals and instrumental. split_lead_backing: lead vocal, backing vocals, instrumental, and the instrumental with backing vocals. remove_noise: background noise out of a voice recording. remove_reverb: room echo and reverb out of a voice recording. enhance_vocal: a clearer phone-recorded or noisy vocal, keeping the singer's voice."
    • changedInput schema / properties / tool / enum
      Previous value: -[
      -  "split_stems",
      -  "split_lead_backing",
      -  "remove_noise",
      -  "remove_reverb"
      -]New value: +[
      +  "split_stems",
      +  "split_lead_backing",
      +  "remove_noise",
      +  "remove_reverb",
      +  "enhance_vocal"
      +]
  4. Changed3 schema fields changed
    • changedOutput schema / properties / outputs / items / required
      Previous value: -[
      -  "stem",
      -  "name",
      -  "description",
      -  "downloadUrl"
      -]New value: +[
      +  "stem",
      +  "name",
      +  "downloadUrl"
      +]
    • changedOutput schema / properties / upload / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "headers": {
      -        "additionalProperties": {
      -          "type": "string"
      -        },
      -        "propertyNames": {
      -          "type": "string"
      -        },
      -        "type": "object"
      -      },
      -      "method": {
      -        "const": "PUT",
      -        "type": "string"
      -      },
      -      "receivedBytes": {
      -        "maximum": 9007199254740991,
      -        "minimum": -9007199254740991,
      -        "type": "integer"
      -      },
      -      "url": {
      -        "format": "uri",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "method",
      -      "url",
      -      "headers",
      -      "receivedBytes"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "headers": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "propertyNames": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "method": {
      +        "const": "PUT",
      +        "type": "string"
      +      },
      +      "receivedBytes": {
      +        "maximum": 9007199254740991,
      +        "minimum": -9007199254740991,
      +        "type": "integer"
      +      },
      +      "url": {
      +        "format": "uri",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "method",
      +      "url",
      +      "headers"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "id",
      -  "tool",
      -  "toolName",
      -  "status",
      -  "price",
      -  "upload",
      -  "outputs",
      -  "pollAfterSeconds",
      -  "websiteUrl",
      -  "links"
      -]New value: +[
      +  "id",
      +  "tool",
      +  "toolName",
      +  "status",
      +  "upload",
      +  "outputs",
      +  "pollAfterSeconds",
      +  "websiteUrl",
      +  "links"
      +]
  5. Changed1 schema field changed
    • removedOutput schema / properties / price / const
      Removed value: -"free"
  6. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), it discloses the quota model (one free use per tool per network), the five-minute duration limit, the account-vs-free billing path, and the asynchronous upload protocol: it returns an upload URL, you PUT the file, then poll get_free_audio_job. These are the operational facts an agent needs and none are in the annotations.

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?

Three sentences, front-loaded with the capability list, then quota constraints, then the upload handshake. Wording is dense but almost every clause carries information; the aside 'as on the website' is the only clause that does not earn its place.

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

Completeness5/5

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

For a six-parameter, nested-object, open-world job-creation tool with an output schema, the description covers the capability set, the quota and length limits, the auth/billing path, and the full upload-then-poll sequence. Return values are already covered by the output schema, so nothing essential is missing.

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 coverage is 100% and the schema already explains every parameter, including the tool enum variants, the optional attached-audio object, and the duration/size fields. The description adds only the upload handshake around the URL, not new meaning for individual parameters, so the baseline 3 applies.

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 first sentence names the concrete operations (split stems, isolate vocals, split lead from backing, remove noise/reverb, enhance vocal) and the title scopes it as an audio-processing job. It also names the sibling get_free_audio_job as the completion step, so an agent can place it in the workflow without opening a schema.

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

Usage Guidelines4/5

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

It states the conditions under which this free tool applies: no account/API key, one free use of each tool per network, and a five-minute file cap, plus the note that a connected account runs it on that account's plan. That is clear context, but it never explicitly says to use create_audio_job when an account exists or when the file exceeds five minutes, so the alternative is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources