Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

soundcloud_artist_tracks

Retrieve tracks for a SoundCloud artist by handle or URL, with cursor-based pagination to fetch more results.

Instructions

soundcloud: Artist Tracks. GET /v1/soundcloud/artist/tracks. Provide one of: handle, url. Gets tracks/songs for a SoundCloud artist by handle or URL. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlNoSoundCloud artist tracks URL. Provide url or handle.
cursorNoCursor to get more tracks. Get 'cursor' from previous response.
handleNoSoundCloud artist handle. Provide handle or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely valuable behavioral trait beyond the schema: costing 1 credit on success, free on errors/cache hits, and a caveat about not-found or empty results. It says nothing about the return shape or payload size, which matters since there is no output schema.

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?

Purpose comes first, then the input rule, then the cost policy. The name and endpoint restatement is conventional but redundant, and the final cost sentence is somewhat legalistic, though it still earns its place for a metered API.

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?

For a three-parameter read tool with no annotations and no output schema, the description covers selection and billing but leaves the agent guessing about the returned data's structure and pagination mechanics beyond the schema's cursor field.

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 the schema already documents url, handle, and cursor. The description only reinforces that handle and url are alternatives ('Provide one of'), which is a small addition over the schema's duplicate 'Provide url or handle' wording.

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 and resource ('Gets tracks/songs for a SoundCloud artist') plus the lookup key (handle or URL), which is enough to distinguish this list operation from a single-track lookup. The name and endpoint are restated before the actual purpose, but the substance is clear.

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?

The 'Provide one of: handle, url' line establishes the input precondition for using the tool, and 'get more tracks' via cursor implies pagination, but there is no explicit when-to-use versus a sibling (e.g., artist profile or search) and no when-not guidance.

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