Skip to main content
Glama

Check an audio job

get_audio_job
Read-only

Use after create_audio_job and the upload, until the job is completed or failed. When complete it lists each output; call get_audio_download for the ones the user wants.

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_audio_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe id returned by create_audio_job.

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: this is a repeated/polling call bounded by completion or failure, and the completed response enumerates outputs. Failure-response detail is left to the output schema.

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, front-loaded with the usage trigger, then the follow-up action. No filler, and every clause conveys either when to call it or what to do with the result.

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?

For a one-parameter read-only polling tool with an output schema and full annotation coverage, the description supplies the lifecycle position, the stop condition, and the next-tool handoff. Only edge-case behavior (invalid id, transitional states) is unaddressed, which is minor here.

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% and the sole parameter jobId is documented in-schema as 'The id returned by create_audio_job.', so the schema carries the weight. The description references the job only implicitly and adds no format or lookup guidance beyond the schema, which is the baseline-3 case.

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 identifies this as the polling/status step in the create_audio_job lifecycle and states what a completed job yields ('lists each output'). The concrete verb 'check status' is only implied via 'Use after create_audio_job ... until the job is completed or failed', so an agent must infer it, but the resource and lifecycle position are unambiguous.

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 a clear sequencing rule (call after create_audio_job and the upload) and a termination condition (until completed or failed), plus routes the agent to get_audio_download for outputs the user wants. It stops short of stating what to do on a not-yet-started job or how to handle an invalid jobId, so it is strong but not exhaustive.

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