Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get my uploads

get_my_tracks
Read-only

List the connected user's SoundCloud uploads in ascending or descending date order, with optional result limits and verbose field details.

Instructions

List the connected user's uploads. Sort: asc for oldest first, desc for newest.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
next_hrefNoNext page URL; pass to next_page
collectionYesPage items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the ordering behavior (asc = oldest first, desc = newest), but says nothing about authentication requirements, the 200-item cap, or what happens when the result set is truncated.

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?

Two short sentences with the scope front-loaded and no filler. The sort explanation earns its place, though the fragment style ('Sort: asc for oldest first') trades a little readability for brevity.

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

Completeness3/5

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

An output schema exists, so return shape needn't be explained, and the read-only nature is annotated. Still, for a list tool with a capped limit and pagination available via next_page, the description omits how to page through results and what auth prerequisite ('connected user') implies.

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 only 33% — only 'verbose' carries a schema description. The description compensates for 'sort' by explaining what asc and desc mean chronologically, which is genuine added value, but it ignores 'limit' entirely (default 50, max 200 are left to the schema) and says nothing about 'verbose'.

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 and resource ('List the connected user's uploads'), and the word 'connected' scopes it to the authenticated account, which separates it from the sibling get_user_tracks that takes a user. It never names that sibling explicitly, so the differentiation is implied rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it should call this when it wants the current user's own uploads rather than someone else's. There is no explicit when-to-use or when-not guidance, no mention of how it relates to get_user_tracks, get_my_likes, or the pagination sibling next_page.

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

Deploy Server

Other Tools