ScrapeCreators MCP Server

Track

soundcloud_track

Fetch detailed SoundCloud track metadata by URL—title, plays, likes, reposts, comments, artwork, artist—after confirming a paid API call.

Instructions

Fetches detailed information about a SoundCloud track/song by URL. Returns track title, plays, likes, reposts, comments, artwork, artist, and other SoundCloud metadata. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

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_track"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	SoundCloud track URL.
`account`	No	Named private ScrapeCreators account; selects credentials, not a remote account ID.
`confirm`	No	Must be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Oct 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With annotations marking readOnlyHint=false and idempotentHint=false, the description adds genuinely useful context the annotations don't: it consumes paid API credits, requires confirm=true, and explains that this read-like POST does not publish to social platforms. That resolves the ambiguity of a non-readOnly annotation on a fetch tool. It stops short of stating rate limits or credit amounts.

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?

Three tight sentences with the core purpose front-loaded and the credit/confirm caveat immediately after. No filler, though the return-field enumeration is slightly listy.

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?

No output schema exists, so the description compensates by naming the returned fields (title, plays, likes, reposts, comments, artwork, artist). Annotations cover safety and the description covers credits and confirm, leaving only rate-limit/credit-cost specifics unstated.

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 url, account, and confirm are already documented in the schema. The description restates the confirm requirement but adds no syntax or format detail beyond it. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clear verb+resource ('Fetches detailed information about a SoundCloud track/song by URL') and enumerates the returned fields. It does distinguish the track entity implicitly from soundcloud_artist, but never explicitly names the sibling it is not, so it falls short of a 5.

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?

No when-to-use guidance, no conditions selecting this over soundcloud_artist_tracks or spotify_track. The only conditional statement is the confirm=true requirement, which is a parameter constraint rather than usage routing.

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

Deploy Server