Skip to main content
Glama
Sign In

SoundCloud MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List comments in SoundCloud

soundcloud_list_comments
Read-onlyIdempotent

List comments in the user's own SoundCloud account from ChatGPT, Claude or any AI agent. Returns how to do it in SoundCloud step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's SoundCloud Cloud Browser. SoundCloud's official API: SoundCloud has a public API, but you need an Artist Pro subscription to register an app and get credentials (checked 30 Oct 2026).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive; the description adds real context beyond them — that nothing is opened by the call itself, that the return value is a step-by-step guide with screens/buttons/fields, and that the official API requires an Artist Pro subscription for credentials. That last point usefully explains why the browser-assisted route is used.

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

Conciseness3/5

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

The core facts (returns a guide, opens nothing, then use cotlet_browser_*) are present but buried in a long, clause-heavy sentence. The 'from ChatGPT, Claude or any AI agent' phrase and the dated API aside add bulk without helping selection, and the key sequencing is not front-loaded.

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 zero-parameter, no-output-schema tool the description supplies what an agent needs: what is returned, that no side effect occurs, and which tools complete the workflow. Only the absence of sibling differentiation keeps it short of full completeness.

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 the baseline is 4 and there is nothing for the description to disambiguate. The parenthetical about screens, buttons, and fields describes returned content rather than inputs, so it neither helps nor harms this dimension.

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?

States a specific verb and resource (list comments) scoped to the user's own SoundCloud account, and discloses that the tool itself does not perform the listing but returns step-by-step guidance. There is mild tension between the imperative name and the 'returns how to do it step by step' behavior, but the agent can still determine what comes back.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says the follow-up action must be carried out with the cotlet_browser_* tools in the user's SoundCloud Cloud Browser, which gives a clear usage path. It does not, however, contrast this tool against siblings like soundcloud_read_direct_messages or soundcloud_list_tracks, so the routing guidance is incomplete.

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

All SoundCloud MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources