SoundCloud MCP Server

Overview Schema Source Related Servers Discussions Admin

Get an artist's links

get_user_web_profiles

Read-only

Retrieve the external links listed on a SoundCloud user's profile, including websites and social accounts, to identify their official channels.

Instructions

List the external links on a user's profile, such as a website or socials.

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": {
      "userId": "<userId>"
    },
    "name": "get_user_web_profiles"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`userId`	Yes

Output Schema

Name	Required	Description	Default
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.2Nov 9, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description need not restate it. The description adds only that the links are external (website/socials), and says nothing about pagination behavior despite a limit parameter, nor about what happens for a user with no links.

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?

A single front-loaded sentence with no filler; the resource and scope come first. The only softness is the hedging phrase "such as", which slightly weakens a list that is presumably exhaustive of link types.

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?

An output schema exists, so return values need no explanation. However, for a two-parameter tool with zero schema documentation, the description leaves the ID format and the limit/pagination semantics unexplained, which is a meaningful gap for an agent building the call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden and does not. It never explains that userId is required or that it accepts either a numeric ID or a string, and the limit parameter (default 50, max 200) is entirely unmentioned.

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 the external links on a user's profile") and gives concrete examples ("website or socials"). This clearly separates it from siblings like get_user, get_user_tracks, or get_profile, though it never names those siblings explicitly.

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?

There is no when-to-use or when-not-to-use guidance. With a sibling named get_profile that plausibly also surfaces profile links, the agent is left to infer which tool to call. No prerequisites or alternative routes are mentioned.

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

Deploy Server