Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Connect SoundCloud

connect_soundcloud

Log in to SoundCloud through your browser and save the access token so future sessions can authenticate without repeating sign-in.

Instructions

Log in through your browser and save the token for future sessions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations only say the tool is not read-only and is open-world; they do not reveal that a browser window is launched or that a token is persisted. The description supplies both facts, which is meaningful context beyond the structured fields. It stops short of covering interactivity (does the call block until the user finishes?) or failure behavior, which matters for an openWorldHint tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single sentence with the mechanism (browser login) front-loaded before the effect (saved token). Every clause carries information and there is no filler.

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 no-parameter, no-output-schema connection tool, the description covers the essential mechanics an agent needs: it is interactive, it authenticates, and it persists credentials for later calls. The remaining gap is what the agent should do around it — verify with auth_status or expect a wait — but nothing critical is missing.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a no-arg tool 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 action set — browser login plus token persistence — so the agent knows exactly what the tool accomplishes. It does not name the related siblings (auth_status, sign_out) that would let the agent place it precisely within the auth lifecycle.

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 authentication step to run before authenticated calls, but the description never says when to call it versus checking auth_status first or when to prefer sign_out. No preconditions or exclusions are stated.

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