Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get my followers

get_my_followers
Read-only

Lists the users who follow the connected SoundCloud account, letting you review followers with an optional limit and verbose field detail.

Instructions

List the users who follow the connected user.

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

Input Schema

NameRequiredDescriptionDefault
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.1/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds little behavioral context beyond the resource being listed. It does not mention authentication requirements explicitly, pagination behavior, rate limits, or how 'limit' affects the returned follower list.

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 front-loaded sentence with zero filler. Every word contributes to identifying the action and the target account.

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 low-complexity and has an output schema, so the description does not need to explain return values. However, it leaves gaps around when to use this versus get_user_followers and around the undocumented 'limit' parameter, making it only minimally complete for an agent.

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 description coverage is only 50%: 'verbose' is documented in the schema, while 'limit' has no description. The tool description does not compensate by explaining either parameter, so it adds no semantic meaning beyond the structured schema.

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 clear verb and resource: list the users who follow the connected user. The phrase 'connected user' implicitly distinguishes this from get_user_followers, which targets an arbitrary user, but it does not explicitly name that sibling.

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 use of 'my' and 'connected user' implies this is for the currently authenticated account, but there is no explicit when-to-use guidance, prerequisite note, or comparison against get_user_followers. Usage is therefore only inferable.

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