Runs full diagnostic analysis on multiple files in a single call. Processes up to 50 files sequentially, one at a time, and returns the full diagnostic result for each file. Sample rate mismatches across the batch are flagged as dealbreaker severity in every file’s results, not just the mismatched ones.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
| file_paths | list[string] | required | List of paths to audio files (max 50) |
Example Output
Illustrative summary; MCP responses use structured JSON.
$ batch_diagnostic [vocals.wav, drums.wav, bass.wav, keys.wav]
Batch Diagnostic: 4 files
vocals.wav Loudness: -18.4 LUFS | Peak: -3.2 dB | Centroid: 2,847 Hz Problems: significant sibilance at 6.8 kHz
drums.wav Loudness: -12.1 LUFS | Peak: -0.4 dB | Centroid: 1,423 Hz Problems: None
bass.wav Loudness: -16.7 LUFS | Peak: -2.8 dB | Centroid: 185 Hz Problems: moderate mud 200-350 Hz
keys.wav Loudness: -20.3 LUFS | Peak: -6.1 dB | Centroid: 3,102 Hz Problems: None
What the Numbers Mean
Batch diagnostic returns the same full diagnostic result for every file — all six analysis dimensions (spectral, loudness, dynamics, stereo, phase, problems), identical in shape to full_diagnostic. The output above is trimmed to the highlights for readability.
- Per-file problems — Quick identification of which stems need treatment before mixing begins.
- A file that fails to load or analyze comes back as
{"error": "...", "error_type": "..."}in place of a result, after batch-level validation succeeds. Invalid batch arguments or an exceeded aggregate memory limit can reject the whole call. - Sample rate mismatch — If the files in the batch don’t share a sample rate, batch_diagnostic injects a dealbreaker-severity problem into every file’s
problemsfield, not just the mismatched ones — a session-wide rate mismatch affects the whole mix.
See full_diagnostic for complete metric descriptions.
Example Prompts
Session overview
Analyze all the stems in my session: vocals.wav, drums.wav, bass.wav, guitar.wav, keys.wav, strings.wav
Quick scan
Run a batch diagnostic on everything in my recordings folder
Related Tools
- full_diagnostic — The same six analysis dimensions for one file
- multi_stem_masking — After batch diagnostic, check for frequency conflicts between stems
Pro tip
Run batch diagnostic before starting a mix session. It gives you a bird’s-eye view of all your material: relative loudness, which tracks have issues, and where the potential trouble spots are. Your AI assistant can then prioritize what to fix first.