Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

soundcloud_profile

Fetch a SoundCloud user or artist profile from a full profile URL and return username, bio, avatar, location, verification, follower, track, playlist, and like counts.

Instructions

Get a SoundCloud user/artist profile. Returns a SoundCloud user or artist profile for a full profile url such as https://soundcloud.com/artist. Fields are username, full name, bio, avatar, city, country, verified status, and counts of followers, followings, tracks, playlists and likes. A URL for a track or other entity returns 400; an unresolvable URL returns 404.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Full soundcloud.com user/artist profile URL

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.0Aug 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden, and it does add real context: it enumerates returned fields and specifies failure semantics (400 for track/other entities, 404 for unresolvable URLs). Auth requirements, rate limits, and pagination are not mentioned, which keeps it from 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.

Conciseness4/5

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

Front-loaded with purpose, then parameter format, then return fields and error cases in four tight sentences with no filler. The field enumeration is dense but useful given the lack of an output schema.

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?

With no annotations and no output schema, the description steps in to cover input shape, the full list of returned fields, and both failure modes, so an agent has everything needed to invoke it and interpret the result correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by giving a concrete example URL pattern (`https://soundcloud.com/artist`) and by defining the validation behavior of invalid URLs (400/404). It documents how the single parameter is expected to be shaped.

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?

States a specific verb+resource ('Get a SoundCloud user/artist profile') and distinguishes the entity from related siblings (tracks, playlists) by noting that a track/other-entity URL returns 400. An agent can tell this is a profile lookup, not a track or playlist fetch, without opening the schema.

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?

Usage is implied through the required input format ('full profile url such as https://soundcloud.com/artist') and the error rule that non-profile URLs fail, which indirectly routes the agent to other SoundCloud tools. However, it never explicitly names alternatives (e.g., soundcloud_track) or states when-not-to-use conditions, leaving that to inference.

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

Deploy Server