Skip to main content
Glama

Get job status

get_job
Read-only

Retrieve job status, progress, and results for audio mastering, cleanup, or preview tasks. For completed masters, get a signed download link to fetch the final file.

Instructions

Status, progress and result metrics (after_lufs, true_peak_db, lra, platform_ready) for a mastering, cleanup or preview job. For previews it returns each style with its loudness and a listen link. When a master is done it also returns download_url — a signed link that works without credentials for about an hour, so an OAuth-connected agent can fetch the file it paid for. Free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
lraNo
errorNo
statusNo
progressNo
after_lufsNo
result_urlNo
download_urlNosigned, ~1 h, works without credentials
true_peak_dbNo
platform_readyNo
download_url_expires_inNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds valuable context beyond that: previews return per-style loudness and listen links, completed masters return a download_url, the signed link expires after about an hour, no credentials are needed to fetch it, and the operation is free. This strongly supports correct agent behavior.

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?

The description is compact and front-loaded, starting with the core purpose before adding conditional details. Every sentence earns its place: general metrics, preview-specific behavior, and master download/auth behavior.

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 read-only tool with an output schema, the description covers the essential agent-facing context: what metrics are returned, how previews differ, when a download URL appears, its validity window, authentication requirements, and pricing. Nothing critical is missing.

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 single parameter job_id has no schema description, and the description does not explain where the job_id comes from or how to format it. It is only implicitly tied to 'a mastering, cleanup or preview job,' so the description does not compensate for the 0% schema coverage.

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 description clearly identifies the tool's purpose: retrieving status, progress, and result metrics for mastering, cleanup, or preview jobs. It lists specific metrics and distinguishes behavior by job type, making its scope unambiguous even among siblings like master_track or preview_styles.

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

Usage Guidelines3/5

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

The description implies this is the follow-up tool to check a job's outcome, and it gives conditional context for previews and finished masters. However, it never explicitly states when to use this tool versus alternatives, nor does it mention what it is not for.

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