Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Get track

get_track
Read-only

Retrieves details for a single SoundCloud track by ID, returning a compact summary by default or every available field when verbose is enabled.

Instructions

Get details for one track.

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": "get_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackIdYes
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.1.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / trackId / minimum
      Removed value: -1
    • changedInput schema / properties / trackId / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
    • addedInput schema / properties / verbose
      Added value: +{
      +  "default": false,
      +  "description": "Return every field SoundCloud sends, such as descriptions, not the compact summary",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. Beyond that, the description adds nothing: it does not say what fields come back, whether results can be missing/private, or how it differs from the list-style track tools.

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 single sentence is front-loaded and free of waste, but its brevity comes at the cost of under-specification rather than efficiency. There is no structure to speak of because there is almost no content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what 'details' means, and it does not — no mention of the compact-vs-full response behavior implied by 'verbose' or of failure cases. For a lookup tool in a crowded sibling set, this is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: 'verbose' is documented in the schema, but 'trackId' has no description and accepts either a string or a number with no explanation of valid formats (numeric ID vs. URN vs. permalink). The description supplies no parameter meaning at all, so it fails to compensate for the gap.

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 gives a specific verb ('Get') and resource ('details for one track'), so an agent immediately knows this is a single-item lookup. It does not, however, distinguish itself from siblings such as search_tracks, get_playlist_tracks, or get_related_tracks, which can also surface track data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the many other track-returning siblings, nor any note about prerequisites such as needing a track ID obtained elsewhere. The only implied usage is 'you have one track and want its details.'

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