Skip to main content
Glama
jamiew

SoundCloud MCP Server

Follow user

follow_user
Idempotent

Follow a SoundCloud user by providing their user ID to add them to your network and receive updates.

Instructions

Follow a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdYes
Behavior2/5

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

Annotations indicate this is a mutable, idempotent operation (readOnlyHint false, idempotentHint true), but the description adds no behavioral context beyond what annotations already provide. It does not disclose side effects, permissions needed, or potential errors.

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 description is very short at four words, which is concise but lacks essential information. It is front-loaded and efficient but sacrifices substance for brevity.

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?

For a simple follow action with a single parameter and no output schema, the description is minimally adequate. However, it omits important context such as whether the tool returns any confirmation or error messages, and it does not account for the openWorldHint annotation implying external effects.

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?

The input schema has one parameter 'userId' with a numeric type and minimum constraint, but no description is provided in the schema (0% coverage). The tool description also fails to add any meaning beyond the parameter name, leaving the agent without guidance on what value to supply.

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 'Follow a user' clearly states the verb and resource, making the purpose obvious. However, it does not differentiate from sibling tools like 'unfollow_user' or 'like_track', which could cause confusion for an AI agent selecting among similar actions.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'unfollow_user' or other social actions. The description lacks context about prerequisites like authentication or whether the user must be logged in.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jamiew/soundcloud-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server