Skip to main content
Glama
llyfn

Spotify MCP Server

follow_artists_or_users

Follow one or more artists or users on Spotify by providing their IDs and the follow type.

Instructions

Follow one or more artists or users. Auto-chunks at 50 IDs per request.

    Args:
        follow_type: "artist" or "user".
        ids: List of Spotify artist or user IDs (not URIs).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
follow_typeYes
idsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description includes some behavioral traits: auto-chunking at 50 IDs and that IDs should not be URIs. However, it does not disclose effects, errors, or rate limits.

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?

Description is short (3 lines), front-loaded with the main purpose, and every sentence adds value. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite missing annotations and low schema coverage, the description covers input semantics and auto-chunking. For a simple tool with an output schema, it is reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description compensates by explaining 'follow_type' can be 'artist' or 'user' and that 'ids' are Spotify IDs, not URIs. Adds meaning beyond the schema's title and type fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Follow one or more artists or users' with specific verb and resource. It distinguishes from sibling tools like 'unfollow_artists_or_users', 'check_following', and 'get_followed_artists'.

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 on when to use this tool vs alternatives like 'check_following' or 'get_followed_artists'. The description does not mention prerequisites or when not to use it.

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/llyfn/spotify-mcp'

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