MCP tools
Your connected client's tools/list response gives the exact tool names, inputs, and permissions available to your account. This page helps you find the main music and campaign workflows.
| Area | What you can explore |
|---|---|
| Music library | Account tracks, versions, and saved release details. |
| Music analysis | Existing track reports and the supported account analysis workflow. |
| Campaigns | Campaign details, recipient activity, feedback, and supported draft preparation. |
| Contacts and playlists | Lists and music-sharing organization within your account permissions. |
| Account context | The available company context and runtime information needed before account actions. |
Representative customer tools
The following names are starting points. Check your connected catalog for the current inputs and availability; narrower client profiles can expose fewer tools.
| Tool | Purpose |
|---|---|
droptrack_list_companies | Identify your available account/company contexts. |
droptrack_list_tracks | Read a page of tracks in the connected company. |
droptrack_get_track_details | Read a track's saved details and versions. |
droptrack_get_track_analysis | Read existing structured analysis, with optional readiness status. |
droptrack_list_campaigns | Find campaigns in the connected company. |
droptrack_get_campaign_analytics | Inspect campaign activity. |
droptrack_get_comments | Read timestamped comments for a track, playlist, or campaign. |
droptrack_create_audio_analysis_upload | Prepare a short-lived audio upload within account limits. |
droptrack_analyze_audio | Start the supported analysis workflow, which can save music to your account. |
Example tool call
Inside an already authorized MCP session, a tools/call request uses a tool name and its arguments. For example, the parameters for a first track-list read are:
json
{
"name": "droptrack_list_tracks",
"arguments": { "limit": 20, "cursor": 0 }
}This is an MCP request example, not a REST endpoint or a complete custom-client authentication quickstart. The current track-list schema permits limit from 1 to 100 and a nonnegative offset cursor. Use IDs returned by your own account for follow-up reads. Inspect isError and the returned content before treating any operation as successful. Keep private audio URLs and account data in your authorized client.
Read the tool before using it
The catalog describes inputs and structured results. Tool annotations distinguish reads, writes, potentially destructive actions, and operations involving external services. Confirm the meaning of a result: accepting a background job is not the same as completing analysis.
The exact tools offered can differ by client catalog profile, role, entitlement, or environment. A tool's presence does not grant every requested action. Do not supply another company ID to work around the authorized company context.
Production endpoint
text
https://mcp.droptrack.com/mcpUse the standard production connection unless your provider's published setup requires a narrower catalog. Setup instructions remain in the help center.
REST reference
DropTrack currently offers a public MCP connection. A public REST API and self-service API keys are not available. Tell us what you want to build if your product needs HTTP endpoints.