Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check if I follow a user

is_following
Read-only

Check if the connected SoundCloud user follows a specific user; unknown users are treated as not followed. Use it to verify follow status before social actions.

Instructions

Check whether the connected user follows a user. Unknown users count as not followed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>"
    },
    "name": "is_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes

Output Schema

NameRequiredDescriptionDefault
followingYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), but the description adds a genuinely useful behavioral fact: unknown users resolve to 'not followed' rather than raising an error. That edge-case behavior is not derivable from the schema or annotations and directly affects how an agent should interpret a negative result.

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?

Two short sentences, zero filler, with the core predicate stated first and the edge case second. Nothing could be removed without losing information.

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-value explanation is unnecessary, and the unknown-user behavior is covered. However, for a tool with a fully undocumented parameter of ambiguous type, the definition leaves the most error-prone detail (what to pass as userId) unaddressed.

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 0%, and the single parameter accepts string OR number with no explanation. The description does not say whether userId is a numeric ID, a permalink, or a username, nor why both types are allowed. Since the schema is silent, the description had to compensate and does not.

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 ('check whether the connected user follows a user'), which clearly separates it from list-style siblings like get_my_followings and mutation siblings like follow_user/unfollow_user. It does not explicitly name an alternative, but the predicate nature of the tool is unmistakable from the name and first sentence.

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 single-relationship check as opposed to enumerating followings via get_my_followings. There is no explicit guidance on when to prefer this over the list tool, nor any prerequisite or rate-limit context.

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