Skip to main content
Glama
superseoworld

MCP Spotify Server

get_featured_playlists

Retrieve Spotify's featured playlists to discover curated music collections. Filter results by locale, limit, and offset for customized browsing.

Instructions

Get a list of Spotify featured playlists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoOptional. Desired language (format: es_MX)
limitNoOptional. Maximum number of playlists (1-50)
offsetNoOptional. Index of the first playlist to return

Implementation Reference

  • The core handler function that implements the logic for fetching featured playlists from the Spotify Browse API endpoint /browse/featured-playlists, constructing query parameters from input args.
    async getFeaturedPlaylists(args: GetFeaturedPlaylistsArgs) {
      const { locale, limit, offset } = args;
    
      const params = {
        ...(locale !== undefined && { locale }),
        ...(limit !== undefined && { limit }),
        ...(offset !== undefined && { offset })
      };
    
      return this.api.makeRequest(
        `/browse/featured-playlists${this.api.buildQueryString(params)}`
      );
    }
  • TypeScript interface defining the optional input parameters (locale, limit, offset) for the get_featured_playlists tool.
    export interface GetFeaturedPlaylistsArgs {
      locale?: string;
      limit?: number;
      offset?: number;
    }
  • src/index.ts:640-663 (registration)
    Registration of the get_featured_playlists tool in the MCP server's ListTools response, including name, description, and input schema.
    {
      name: 'get_featured_playlists',
      description: 'Get a list of Spotify featured playlists',
      inputSchema: {
        type: 'object',
        properties: {
          locale: {
            type: 'string',
            description: 'Optional. Desired language (format: es_MX)'
          },
          limit: {
            type: 'number',
            description: 'Optional. Maximum number of playlists (1-50)',
            minimum: 1,
            maximum: 50
          },
          offset: {
            type: 'number',
            description: 'Optional. Index of the first playlist to return',
            minimum: 0
          }
        }
      },
    },
  • src/index.ts:885-891 (registration)
    Dispatch logic in the CallToolRequestSchema handler that validates arguments and delegates to the playlistsHandler.getFeaturedPlaylists method.
    case 'get_featured_playlists': {
      const args = this.validateArgs<GetFeaturedPlaylistsArgs>(request.params.arguments || {}, []);
      const result = await this.playlistsHandler.getFeaturedPlaylists(args);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does at a high level without mentioning authentication requirements, rate limits, pagination behavior (despite offset/limit parameters), response format, or whether this is a read-only operation. For a tool with 3 parameters and no annotation coverage, this is insufficient.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and gets straight to the point with zero wasted verbiage.

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

Completeness2/5

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

For a tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what 'featured' means, how results are structured, authentication requirements, or typical use cases. The agent would need to guess about important behavioral aspects despite having complete parameter documentation in the schema.

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 100%, so the schema already documents all three parameters thoroughly with descriptions, types, and constraints. The description adds no additional parameter information beyond what's in the schema, which meets the baseline expectation when schema coverage is complete.

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 clearly states the action ('Get a list of') and resource ('Spotify featured playlists'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_category_playlists' or 'get_current_user_playlists' by explaining what makes 'featured' playlists distinct.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of when featured playlists are appropriate versus other playlist retrieval tools like 'get_category_playlists' or 'get_current_user_playlists', nor any context about what 'featured' means in Spotify's ecosystem.

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

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