Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get my reposts

get_my_reposts
Read-only

List tracks or playlists reposted by the connected SoundCloud user, with controls for result limit, content type, and compact or full metadata output.

Instructions

List tracks or playlists the connected user has reposted.

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

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

B3/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 no behavioral context beyond the annotations: it doesn't mention the authentication requirement implied by 'connected user', the default/max result size, result ordering, or whether the list is paginated.

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 terseness leaves no room for the routing or parameter detail the tool needs.

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 not be described, and the tool is a simple read. Still, for a listing endpoint with a limit cap and a verbose toggle, an agent would benefit from knowing about pagination behavior and the auth context, neither of which is present.

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 33% — 'kind' and 'limit' have no field descriptions, and only 'verbose' is documented in the schema. The description mentions tracks vs. playlists but merely restates the enum values already visible in the schema, and says nothing about limit semantics or what 'verbose' costs in payload size.

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 ('List') and resource ('tracks or playlists the connected user has reposted'), which is far more informative than the title alone and implicitly separates it from the sibling get_user_reposts by scoping to the authenticated user. It never names that sibling explicitly, so the differentiation is inferential rather than stated.

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 phrase 'the connected user' implies this is the authenticated-user variant, which is the key selection cue among siblings. However, there is no explicit when-to-use vs. get_user_reposts or get_my_likes, and nothing about pagination despite a next_page sibling being available.

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