Skip to main content
Glama
thenavidm

ScrapeCreators MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Artist Tracks

soundcloud_artist_tracks

Fetches a SoundCloud artist's tracks by handle or URL and returns profile, track list, and pagination info; requires confirm=true for paid calls.

Instructions

Fetches tracks/songs for a SoundCloud artist by handle or URL. Returns the artist profile, track list, and pagination info from SoundCloud. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoSoundCloud artist tracks URL. If you'd prefer to use the handle instead, you can use the handle parameter instead.
cursorNoCursor to get more tracks. Get 'cursor' from previous response.
handleNoSoundCloud artist handle. If you'd prefer to use the URL instead, you can use the url parameter instead.
accountNoNamed private ScrapeCreators account; selects credentials, not a remote account ID.
confirmNoMust be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations set readOnlyHint=false, which on its own could wrongly suggest a mutating operation; the description proactively reconciles this by explaining that read-like POST requests do not publish to social platforms. It also discloses the credit cost and the confirm=true requirement, which annotations do not cover.

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 short sentences, front-loaded with what the tool returns before the cost/prerequisite caveats. No filler, though the trailing clause about POST requests is slightly awkward in placement.

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?

With no output schema, the description usefully names the return payload (artist profile, track list, pagination info). Combined with the credit/confirm disclosure, an agent has enough to call it correctly and interpret the result.

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 description coverage is 100%, so all five parameters are already documented, including the url/handle alternates and the confirm requirement. The description restates handle/URL usage without adding format or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific verb (fetches) and resource (tracks/songs for a SoundCloud artist) plus the accepted identifiers (handle or URL). It is distinguishable from soundcloud_artist and soundcloud_track by implication, but no sibling is named explicitly, so it stops 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 Guidelines3/5

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

It conveys operational prerequisites (requires confirm=true, consumes paid credits) which helps decide whether to invoke it. However it gives no explicit when-to-use / when-not-to-use guidance relative to soundcloud_artist (profile only) or soundcloud_track (single track), leaving the routing inference to the agent.

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