Crawlora MCP

soundcloud_user_tracks

Read-only

Fetch one SoundCloud artist's own uploaded track items, newest first, with title, artwork, and playback/like/comment/repost counts from canonical user url. Use soundcloud_track for one track, soundcloud_search for catalog search, or soundcloud_playlist for a playlist.

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": {
      "url": "<url>"
    },
    "name": "soundcloud_user_tracks"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Full soundcloud.com user/artist profile URL
`limit`	No	Number of tracks to return (default 20, max 50)

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 7, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Number of tracks to return (default 20, max 50)"
```
- addedInput schema / properties / url / description
```
Added value: +"Full soundcloud.com user/artist profile URL"
```
First observedOct 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description still adds useful behavior: results are ordered newest first, are scoped to the artist's own uploads, and include title, artwork, and playback/like/comment/repost counts. It stops short of describing pagination or rate limits, keeping it below a 5.

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

Conciseness5/5

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

Two tight sentences, front-loaded with the core action and scope, followed by the disambiguation sentence. Every clause carries information; no filler.

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

Completeness5/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 values need not be fully specified, and the description still summarizes the payload fields. Combined with the annotation-covered safety profile and complete param coverage, nothing an agent needs to call this correctly is missing.

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%, so both url and limit are already documented in the schema, establishing a baseline of 3. The description's reference to a 'canonical user url' mildly reinforces the url parameter but adds no syntax or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Fetch) and resource (one SoundCloud artist's own uploaded track items), and adds scope details like 'newest first' and the returned fields. It also differentiates itself from soundcloud_track, soundcloud_search, and soundcloud_playlist, so the agent can distinguish it from siblings without opening a schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: 'Use soundcloud_track for one track, soundcloud_search for catalog search, or soundcloud_playlist for a playlist.' Each alternative is paired with the condition that selects it, leaving nothing to inference.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.