Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List SoundCloud profile tracks

soundcloud_profile_tracks_list
Read-onlyIdempotent

List a SoundCloud profile's tracks newest first by handle, and use the returned cursor to paginate through additional results.

Instructions

List a SoundCloud profile's tracks, newest first. Requires handle. Returns a list (use cursor when paginated).

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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "soundcloud_profile_tracks_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response.
handleYesRequired. SoundCloud handle whose tracks should be listed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds two useful behavioral facts beyond that: results are ordered newest-first and pagination is cursor-based. It says nothing about authentication needs, rate limits, or result size caps, which are the remaining gaps for an open-world read.

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, front-loaded with the action and the required parameter, with zero filler. The pagination note is compact and earns its place, though the parenthetical phrasing is slightly awkward.

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?

For a five-parameter read tool with fully documented schema and no output schema, the description covers the action, ordering, required input and pagination. It does not mention the analytics/plumbing parameters or shape of the returned list, but those are handled by schema descriptions, so the definition is essentially sufficient.

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 — including the analytics plumbing (`context`, `llm_model`, `conversation_id`) — are already documented in the schema. The description restates the `handle` requirement and clarifies cursor reuse, which is marginal added meaning over the schema; 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?

The description states a specific verb and resource ("List a SoundCloud profile's tracks") plus an ordering guarantee ("newest first"), which is enough for an agent to distinguish it from profile-level or single-track siblings. It does not explicitly name those alternatives, so sibling differentiation is only implied by the resource noun.

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 gives one concrete usage cue — pass `cursor` when the result is paginated — and states the required `handle`. It offers no guidance on when to prefer this over `soundcloud_profile_get` or `soundcloud_track_get`, and no exclusion conditions, so usage is implied rather than spelled out.

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