Skip to main content
Glama

Run any NiceVois audio tool

create_audio_job

Every NiceVois audio tool. With no account: split_stems, split_lead_backing, remove_noise, remove_reverb and enhance_vocal (one free use of each per network, up to five minutes) and convert_format (free). With a connected account every tool runs on that account's plan (a subscriber's unlimited use applies), including generate_harmony (upper and lower harmonies from a solo lead vocal), which needs an account. Returns an upload URL; then use get_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>",
      "fileName": "<fileName>",
      "sizeBytes": "<sizeBytes>"
    },
    "name": "create_audio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYes
fileNameYesThe file's name with its extension.
sizeBytesYesThe file's exact size in bytes.
outputFormatNoAudio tools: wav (default), flac, mp3 or ogg. convert_format (required): wav, mp3, aac (M4A), flac, ogg, or an advanced format such as wav24, alac or aiff.
durationSecondsNoLength in seconds if measured; NiceVois measures the file itself after upload.

Output Schema

NameRequiredDescriptionDefault
idNo
toolNo
errorNo
linksNo
priceNo
stageNo
statusNo
uploadNo
messageNo
outputsNo
fileNameNo
toolNameNo
createdAtNo
websiteUrlNo
durationSecondsNo
pollAfterSecondsNo

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. Changed2 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"
      +  }
      +]
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses quota behavior (one free use per network, five-minute cap), plan-dependent execution, and an account prerequisite for one tool value. The key workflow trait — that this only provisions an upload URL rather than processing audio — is stated, which is exactly the context the annotations cannot convey.

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 enumeration of tools is front-loaded and necessary, and the account/no-account split is efficient. The second half is a long run-on sentence covering plan behavior and harmony, which is dense but still readable and free of filler.

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

Completeness4/5

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

With an output schema present the description need not explain return values, yet it still tells the agent that an upload URL comes back and the next step is get_audio_job, closing the loop for a create-then-poll workflow. What remains unaddressed is how this tool relates to the free-audio-job siblings.

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 80% and the enum values are already listed in the schema, so most parameter meaning is structured data. The description adds a useful gloss on generate_harmony (upper and lower harmonies from a solo lead vocal) and implicitly explains why a tool must be chosen, but says nothing about outputFormat or durationSeconds beyond what the schema documents.

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 names a specific verb (creates a job that runs) and enumerates every supported tool value, so an agent knows exactly what the call does. It does not, however, distinguish itself from the sibling create_free_audio_job even though it spends most of its text explaining free-tier access, which risks ambiguity about which tool handles the no-account case.

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 gives concrete eligibility rules: no-account usage is limited to specific tools with one free use per network up to five minutes, while a connected account runs everything on that plan, and generate_harmony requires an account. It also prescribes the follow-up call to get_audio_job, though it never says when to prefer create_free_audio_job instead.

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