Skip to main content
Glama

DropTrack Get Track Analysis

droptrack_get_track_analysis
Read-only

Read the saved report for the exact track/version without creating another analysis. Ground feedback in returned audio evidence. For SoundCloud, do not add source-acquisition notices or request another upload, and do not make claims about unheard sections. Explain Spotify and metadata-only limitations. For progress checks use statusOnly=true and honor the bounded polling guidance; missing is not proof of a running job. Optional opportunity review links open a review, never send music.

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": {
      "trackId": "<trackId>"
    },
    "name": "droptrack_get_track_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackIdYesTrack ID to inspect
includeRawNoInclude raw analyzer payloads in addition to structured output
statusOnlyNoReturn a compact readiness/status view for post-upload polling
accountTypesNoOpportunity categories to include
trackVersionIdNoOptional track version ID to prioritize
includeOpportunitiesNoAlso return personalized submission opportunities for this track
opportunitiesPerTypeNoMaximum opportunities to return per category

Output Schema

NameRequiredDescriptionDefault
resultNoStructured DropTrack result returned by this tool

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety is covered. The description adds genuinely non-obvious behavioral context: 'missing is not proof of a running job', no source-acquisition notices for SoundCloud, no claims about unheard sections, and that opportunity review links only open a review and never send music. These are useful operational constraints beyond what the structured fields convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded, but the body is a dense grab bag of six directives spanning evidence grounding, platform caveats, polling, and opportunity links. Some fragments are terse to the point of ambiguity ('Ground feedback in returned audio evidence', 'Explain Spotify and metadata-only limitations') and lack clear referents, costing readability.

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?

With an output schema present, return values need not be described, and the description focuses instead on usage and interpretation guardrails. For a 7-parameter read tool it covers the risky paths (polling, opportunities, platform limits) adequately, though it says nothing about the raw payload or version-selection behavior.

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%, so all seven parameters are already documented in the schema, and the baseline of 3 applies. The description only adds context for statusOnly (progress polling) and indirectly for includeOpportunities (review links, never send music); includeRaw, trackVersionId, accountTypes, and opportunitiesPerType get no additional meaning.

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 opening sentence gives a specific verb and resource ('Read the saved report for the exact track/version') and explicitly contrasts with creating a new analysis, which routes the agent away from droptrack_create_audio_analysis_upload. It does not, however, clarify how this differs from the similarly named droptrack_get_track_analytics, leaving some ambiguity between the two read tools.

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 concrete when-to-use guidance for the polling case ('For progress checks use statusOnly=true and honor the bounded polling guidance') and implicitly rules out re-analysis ('without creating another analysis'). It stops short of naming an explicit alternative tool for the re-analyze case or stating hard exclusions beyond the SoundCloud caveat.

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.