Skip to main content
Glama

get_followed_artists

Retrieve your followed artists list from Spotify to manage your collection, create playlists, check for new releases, and analyze your music preferences.

Instructions

Retrieve the complete list of artists that the user actively follows on Spotify.

🎯 USE CASES: • Managing your followed artists collection • Creating playlists from your favorite artists only • Checking for new releases from followed artists • Organizing your music library by preferred artists • Exporting your music taste profile for other platforms

📝 WHAT IT RETURNS: • Complete list of artists you follow • Artist names, images, and genre information • Follower counts and popularity metrics • Follow date and relationship duration • Quick access to each artist's catalog

🔍 EXAMPLES: • "Show me all artists I follow" • "Get my followed artists, limit to 50" • "Who are the artists in my following list?" • "Export my followed artists for playlist creation"

💡 MANAGEMENT TIPS: • Regularly review to unfollow inactive artists • Use this list to check for new releases • Great for creating "favorites only" playlists • Perfect for music taste analysis and statistics

⚠️ REQUIREMENTS: • Valid Spotify access token with user-follow-read scope • User must have followed at least one artist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesSpotify access token for authentication
limitNo

Implementation Reference

  • MCP tool handler function for 'get_followed_artists' that destructures input arguments and calls the SpotifyService method.
      handler: async (args: any, spotifyService: SpotifyService) => {
        const { token, limit = 20 } = args;
        return await spotifyService.getFollowedArtists(token, limit);
      },
    },
  • Input schema definition for the tool using createSchema, validating token and optional limit parameters.
    schema: createSchema({
      token: commonSchemas.token(),
      limit: commonSchemas.limit(1, 50, 20),
    }),
  • SpotifyService helper method implementing the core API call to retrieve user's followed artists via /me/following endpoint.
    async getFollowedArtists(
      token: string,
      limit: number = 20
    ): Promise<{ artists: PagingObject<SpotifyArtist> }> {
      const params = {
        type: "artist",
        limit: Math.min(limit, 50),
      };
      return await this.makeRequest<{ artists: PagingObject<SpotifyArtist> }>(
        "me/following",
        token,
        params
      );
    }
  • Registration of artistTools object (containing get_followed_artists) into the central allTools registry used by the ToolRegistrar for MCP server.
    export const allTools: ToolsRegistry = {
      ...albumTools,
    
      ...artistTools,
    
      ...trackTools,
    
      ...playlistTools,
    
      ...playbackTools,
    
      ...userTools,
    
      ...searchTools,
    };
Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses key behavioral traits: it's a read operation (implied by 'Retrieve'), requires authentication ('Valid Spotify access token'), has scope requirements ('user-follow-read'), and includes prerequisites ('User must have followed at least one artist'). It doesn't mention rate limits or pagination behavior, but covers essential operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose with multiple sections (USE CASES, WHAT IT RETURNS, EXAMPLES, MANAGEMENT TIPS, REQUIREMENTS). While structured, it includes extraneous content like 'MANAGEMENT TIPS' that doesn't aid tool selection. The core purpose is front-loaded, but many sentences don't earn their place for an AI agent.

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?

Given no annotations, no output schema, and 2 parameters with 50% schema coverage, the description does a good job covering purpose, usage, and behavioral context. It explains what the tool returns in detail, compensating for the lack of output schema. However, it could better address parameter details or error conditions.

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

Parameters3/5

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

Schema description coverage is 50% (only 'token' has a description). The description doesn't explicitly discuss parameters, though examples like 'limit to 50' hint at the 'limit' parameter's purpose. It adds minimal value beyond the schema, which already documents 'token' for authentication and 'limit' with constraints. Baseline 3 is appropriate given partial schema coverage.

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 specific action ('Retrieve the complete list of artists that the user actively follows') and resource ('on Spotify'), distinguishing it from sibling tools like get_top_artists or get_artist. The purpose is explicit and unambiguous.

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

Usage Guidelines4/5

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

The 'USE CASES' section provides clear context for when to use this tool (e.g., managing followed artists, creating playlists, checking new releases). However, it doesn't explicitly state when NOT to use it or name specific alternatives among siblings, such as get_top_artists for different artist lists.

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/latiftplgu/Spotify-OAuth-MCP-server'

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