Skip to main content
Glama

Check a free audio job

get_free_audio_job
Read-only

Use this after create_free_audio_job and the upload, no more than every 10 seconds, until the job is completed or failed. When it completes, it lists every output file (for example lead vocal, backing vocals, instrumental) with a download link.

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": {
      "jobId": "<jobId>"
    },
    "name": "get_free_audio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe id returned by create_free_audio_job.

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. 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"
      +]
  3. Changed1 schema field changed
    • removedOutput schema / properties / price / const
      Removed value: -"free"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a safe read-only operation, and the description adds useful behavioral detail: polling cadence, terminal states, and that completion returns every output file with a download link. It omits some operational details such as auth requirements or intermediate status values, but it meaningfully supplements 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both carrying useful information: the first covers timing and polling behavior, and the second covers the completed output. There is no redundant or wasted wording.

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 one-parameter polling tool with an output schema and safety annotations, the description is complete enough to call correctly. It supplies the polling rhythm, termination condition, and output expectation without needing to restate the schema.

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%, so the single jobId parameter is already fully documented as the id returned by create_free_audio_job. The description reinforces the prerequisite relationship but adds no new syntax or format detail beyond the schema.

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 makes clear this is a polling/checking tool for a free audio job created by create_free_audio_job, and it explains the terminal states. It does not explicitly distinguish itself from the sibling get_audio_job, so it falls short of full sibling differentiation.

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 clear usage context: call it after create_free_audio_job and the upload, poll no more than every 10 seconds, and continue until completed or failed. It does not state when not to use it or name an alternative polling tool.

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