Skip to main content
Glama

DropTrack Analyze Audio

droptrack_analyze_audio

Analyze uploaded audio or a supported audio/Spotify/SoundCloud link and save a track or new version. For SoundCloud, do not add source-acquisition notices or request another upload, and do not make claims about unheard sections. Spotify may provide only metadata or an audio preview, not the full song: explain the returned evidence. If queued or timed out, check the saved report using bounded polling, not another upload/analysis request. Opportunity review links do not send music.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "droptrack_analyze_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
s3UrlNoS3 URL for an uploaded audio file, such as s3://bucket/key
titleNoOptional track title used when creating a new DropTrack track
artistNoOptional artist name used when creating a new DropTrack track
trackIdNoExisting DropTrack track ID. When provided, uploaded audio is saved as a new active track version instead of a new track
audioUrlNoDirect HTTPS audio URL. S3 URLs are preferred for private uploads
fileNameNoFilename used to infer audio type when needed
uploadKeyNoupload_key returned by droptrack_create_audio_analysis_upload after the client PUTs the file
audioBase64NoInline base64 audio for small files only
contentTypeNoOptional audio MIME type used when the source does not provide one
providerUrlNoSpotify track URL/URI or SoundCloud URL
accountTypesNoSubmission opportunity categories to return with the analysis
versionLabelNoOptional label when trackId is provided and a new version is created
analysisTimeoutMsNoOptional maximum milliseconds to wait for synchronous analysis before returning the saved track and polling instructions
includeOpportunitiesNoReturn personalized submission opportunities derived from the analysis genres
opportunitiesPerTypeNoMaximum submission opportunities to return per account type

Output Schema

NameRequiredDescriptionDefault
resultNoStructured DropTrack result returned by this tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-destructive operation; the description adds substantive context beyond that — that it persists a track or new version, that Spotify may yield only metadata or a preview, that SoundCloud inputs have source constraints, and what to do on timeout. It does not cover auth/permission requirements or whether a failed save is retried, so it is strong but not exhaustive.

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?

Purpose is front-loaded in the first clause, and the remaining sentences are each tied to a distinct operational constraint. It is dense and runs long, with agent-response-style rules (no source-acquisition notices, no claims about unheard sections) that read as policy rather than tool mechanics, but no sentence 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 15-parameter mutation with an output schema, the description covers the important non-obvious behavior: persistence, provider limitations, and async/timeout handling. The main gap is that all parameters are optional, so it never clarifies what the tool does when called with no audio source.

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% across 15 parameters, so the schema already carries the load. The description adds only marginal semantics, mainly the trackId-means-new-version behavior and the timeout/polling consequence of analysisTimeoutMs, and says nothing about the interplay among the several audio-source parameters.

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 states a specific verb and resource ('Analyze uploaded audio or a supported audio/Spotify/SoundCloud link') and adds the side effect ('save a track or new version'), which distinguishes it from the sibling upload and report-fetch tools. It does not name a sibling explicitly, so it stops short of a 5.

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 when-and-when-not guidance: use bounded polling against the saved report if queued or timed out, rather than issuing another upload/analysis request, and treat opportunity review links as non-submissions. It never explicitly contrasts with droptrack_get_track_analysis or droptrack_create_audio_analysis_upload, leaving that routing to inference.

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.