Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get my feed

get_feed
Read-only

Lists recent tracks and playlists from people the connected SoundCloud user follows, with limits and optional full field details.

Instructions

List recent activity from people the connected user follows: tracks by default, or all for playlists too.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
next_hrefNoNext page URL; pass to next_page
collectionYesPage items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.5/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 safety and scope are covered. The description adds the default feed content (followed users' tracks) but says nothing about pagination, caps, or how the feed is ordered, which matters for a feed-listing tool whose sibling set includes next_page.

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 that front-loads the resource and then the mode-switching behavior. There is no filler and nothing redundant with the title.

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, and the annotations cover the read-only profile. However, for a feed tool with a limit parameter and a next_page sibling, the absence of any pagination or result-size guidance leaves a real gap.

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 coverage is 33%; only verbose is documented in the schema. The description does explain the kind semantics ('tracks by default, or all for playlists too'), which adds real meaning beyond the raw enum, but it leaves limit (default 50, max 200) entirely unexplained. That is a partial compensation, appropriate for a 3.

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 gives a specific verb and resource ('List recent activity from people the connected user follows') and states the scope, which clearly separates it from get_my_likes and get_recently_played. It never names a sibling tool explicitly, so it falls short of full differentiation, but the intent is unambiguous.

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?

The 'tracks by default, or all for playlists too' clause implies when each mode applies, but there is no explicit when-to-use or when-not-to-use guidance relative to adjacent tools such as get_recently_played or next_page. Usage is inferable rather than stated.

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

Deploy Server

Other Tools