mastering

Master a track

master_track

Master one track. Uses 1 CREDIT when the account has a balance; otherwise it runs on the free quota (1 free master per day (UTC), without advanced modules). Returns a job id immediately - poll get_job (typical 20-60 s, up to 10 min with restoration). The source is fetched by this server, so the ceiling here is 100 MB per file. Pass dry_run=true first if you want to see what would be used and the effective settings before anything is spent.

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": {
      "audio_url": "<audio_url>"
    },
    "name": "master_track"
  }
}

Input Schema

Name	Required	Description
`style`	No	Preset key from list_presets, e.g. edm, hiphop, podcast, unlimiter. Default standard.
`bitrate`	No	MP3: 128/192/256/320; OPUS: 128/192.
`dry_run`	No	Do not master: report what this call would use and what settings would apply. Nothing is charged, the file is not even downloaded.
`audio_url`	Yes	Public https URL of the audio file (wav/mp3/flac/m4a). A share link to the page works too — Suno/Udio song pages, Google Drive and Dropbox links are resolved to the file automatically.
`intensity`	No	Multiplier on the preset's multiband compression: 1.0 as designed, 0.5 gentler, 1.5 denser. Values outside 0.5-1.5 are clamped.
`out_format`	No
`dither_type`	No	Dither for 16-bit WAV output: tpdf (default), ns_e or ns_itu (noise-shaped).
`target_lufs`	No	Override the preset target, e.g. -14 for Spotify.
`webhook_url`	No	Public https URL to POST the result to instead of polling.
`denoise_strength`	No	Noise reduction, 0-1. 0 disables.
`remove_watermark`	No	Also run AI artifact cleanup first. Free.
`restore_dynamics`	No	Open up a brickwalled source before mastering (pairs with style unlimiter).

Output Schema

Name	Required	Description	Default
`job_id`	No
`dry_run`	No
`poll_with`	No
`would_charge`	No
`tokens_balance`	No
`nothing_was_charged`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (which only say non-read-only and open-world), the description discloses the credit model and free-quota fallback (1/day UTC, no advanced modules), async job semantics with realistic 20-60 s to 10 min durations, a 100 MB ceiling, and that the file is fetched server-side. It also clarifies that dry_run charges nothing and does not even download the file.

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?

Four sentences, each carrying distinct information (cost, async flow, size limit, safe-preview recommendation), with the core action front-loaded. Some nested parentheticals make it denser than necessary, but nothing is 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?

For a 12-parameter async mutation with an output schema, the description covers cost, latency, size limits, follow-up polling, and the safe preview path. Minor gaps: undefined "advanced modules" and no pointer to check_limits when the quota is exhausted.

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 92%, so parameter meanings are already well documented; the description mainly reinforces dry_run semantics that the schema already states. It adds no format guidance for style, target_lufs, or webhook_url beyond what the schema provides, and leaves "advanced modules" undefined.

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?

"Master one track" states a specific verb and resource, and the word "one" implicitly contrasts with batch_master. It never names a sibling tool though, so the agent must infer the routing rather than read it.

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?

The description prescribes a concrete workflow: call dry_run=true first, then poll get_job, or use webhook_url instead of polling. It does not state when to prefer batch_master or analyze_track/preview_styles over this tool, so context is clear but exclusions are absent.

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

All mastering tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?