SoundCloud MCP Server

Overview Schema Source Related Servers Discussions Admin

Get user

get_user

Read-only

Retrieve a SoundCloud user's public profile by ID, with an option to return all available fields instead of a compact summary for detailed profile lookups.

Instructions

Get a user's public profile.

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

Input Schema

Name	Required	Description	Default
`userId`	Yes
`verbose`	No	Return every field SoundCloud sends, such as descriptions, not the compact summary

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.1.2Nov 9, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / userId / minimum
```
Removed value: -1
```

changedInput schema / properties / userId / type

Previous value: -"number"New value: +[
+  "string",
+  "number"
+]

addedInput schema / properties / verbose

Added value: +{
+  "default": false,
+  "description": "Return every field SoundCloud sends, such as descriptions, not the compact summary",
+  "type": "boolean"
+}

First observedv1.0.0Jul 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the word "public", hinting that private fields are excluded, but says nothing about what happens when a user is not found or how the default compact response differs.

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 short sentence with no wasted wording. It is efficiently front-loaded, though the brevity comes at the cost of the substance scored in other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and an undocumented required parameter, the description should say what a profile contains (especially compact vs verbose) and how to identify the user. It does neither, leaving the agent under-informed for a core read tool.

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 coverage is only 50%: the verbose flag is documented in the schema, but userId has no description in either place. The description mentions no parameters at all, so it fails to compensate for the gap and adds nothing beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb and resource ("Get a user's public profile"), so the basic action is clear. However, it does not distinguish this from the sibling get_profile, nor from get_user_tracks/get_user_likes, leaving an agent unsure which user-fetching tool to pick.

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 guidance, no mention of alternatives like search_users or get_profile, and no prerequisites such as auth. The agent must infer usage entirely.

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

Deploy Server