Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Get my profile

get_profile
Read-only

Retrieve the connected user's SoundCloud profile as a compact summary or with all available fields for detailed account context.

Instructions

Get the connected user's SoundCloud profile.

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

Input Schema

NameRequiredDescriptionDefault
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.2
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / verbose
      Added value: +{
      +  "default": false,
      +  "description": "Return every field SoundCloud sends, such as descriptions, not the compact summary",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

B3.2/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 the safety profile is covered. The description adds nothing further — no mention that authentication is required, what happens when no account is connected, or whether the call hits the network each time. For a tool that can only work in an authenticated session, that omission is the main behavioral gap.

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 or redundancy. It is efficient, though the brevity comes at the cost of the usage and auth context noted above rather than from tight editing of rich content.

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?

The tool is simple — zero required parameters, one optional flag fully documented, annotations present, and no output schema to explain. Against that low complexity the description is adequate, but it omits the authentication prerequisite that governs whether the call can succeed at all.

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%, and the 'verbose' parameter already carries a clear explanation of what it toggles ('every field SoundCloud sends... not the compact summary'). The description contributes nothing about the parameter, so the 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 (Get) and resource (SoundCloud profile) and scopes it to 'the connected user's', which separates it from the many id-based siblings like get_user or get_user_tracks. It stops short of naming an alternative explicitly, so it lands just below the top band.

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 only implied: an agent can infer this is the tool for one's own profile rather than another user's. There is no statement of prerequisites (e.g., that connect_soundcloud/auth_status must come first) or of what to do if unauthenticated.

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