Skip to main content
Glama

search_artists

Search Spotify for artists by name, genre, or keywords to discover new music, find specific performers, or explore talent for playlists and collaborations.

Instructions

Search for artists using names, genres, or keywords to discover new music and talent.

🎯 USE CASES: • Finding artists when you only remember partial names • Discovering artists within specific genres or styles • Locating emerging or independent artists • Building diverse playlists with multiple artists • Researching artists for events or collaborations

📝 WHAT IT RETURNS: • Ranked artist results based on search relevance • Artist names, images, and genre classifications • Popularity scores and follower counts • Links to explore each artist's catalog • External URLs and social media links

🔍 EXAMPLES: • "Search for 'jazz pianist' artists" • "Find artists named 'John'" • "Look for 'indie rock' bands" • "Search for artists from 'Nashville'" • "Find 'female rapper' artists"

💡 SEARCH STRATEGIES: • Use genre keywords: "progressive metal", "folk acoustic" • Include location: "Seattle grunge", "Detroit techno" • Try instrument-specific searches: "saxophone", "violin" • Use descriptive terms: "soulful", "experimental", "classical"

⚠️ REQUIREMENTS: • Valid Spotify access token • Meaningful search keywords for best results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesSpotify access token for authentication
queryYesSearch query for artists (artist name, keywords)
limitNo

Implementation Reference

  • Core handler function that executes the Spotify API search for artists using the /search endpoint with type='artist'.
    async searchArtists(
      token: string,
      query: string,
      limit: number = 20
    ): Promise<SearchResult> {
      const params = {
        q: query,
        type: "artist",
        limit: Math.min(limit, 50),
      };
      return await this.makeRequest<SearchResult>("search", token, params);
    }
  • MCP tool definition and registration for 'search_artists', including title, description, input schema using commonSchemas, and handler wrapper that calls SpotifyService.searchArtists.
      search_artists: {
        title: "Search Artists",
        description: `Search for artists using names, genres, or keywords to discover new music and talent.
    
    🎯 USE CASES:
    • Finding artists when you only remember partial names
    • Discovering artists within specific genres or styles
    • Locating emerging or independent artists
    • Building diverse playlists with multiple artists
    • Researching artists for events or collaborations
    
    📝 WHAT IT RETURNS:
    • Ranked artist results based on search relevance
    • Artist names, images, and genre classifications
    • Popularity scores and follower counts
    • Links to explore each artist's catalog
    • External URLs and social media links
    
    🔍 EXAMPLES:
    • "Search for 'jazz pianist' artists"
    • "Find artists named 'John'"
    • "Look for 'indie rock' bands"
    • "Search for artists from 'Nashville'"
    • "Find 'female rapper' artists"
    
    💡 SEARCH STRATEGIES:
    • Use genre keywords: "progressive metal", "folk acoustic"
    • Include location: "Seattle grunge", "Detroit techno"
    • Try instrument-specific searches: "saxophone", "violin"
    • Use descriptive terms: "soulful", "experimental", "classical"
    
    ⚠️ REQUIREMENTS:
    • Valid Spotify access token
    • Meaningful search keywords for best results`,
        schema: createSchema({
          token: commonSchemas.token(),
          query: commonSchemas.searchQuery("artists (artist name, keywords)"),
          limit: commonSchemas.limit(1, 50, 20),
        }),
        handler: async (args: any, spotifyService: SpotifyService) => {
          const { token, query, limit = 20 } = args;
          return await spotifyService.searchArtists(token, query, limit);
        },
      },
  • Aggregates artistTools (containing search_artists) into allTools registry used by ToolRegistrar for MCP tool exposure.
    ...artistTools,
  • Input schema definition for search_artists tool using createSchema from common schemas.
    schema: createSchema({
      token: commonSchemas.token(),
      query: commonSchemas.searchQuery("artists (artist name, keywords)"),
      limit: commonSchemas.limit(1, 50, 20),
    }),
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by describing what the tool returns (ranked results, artist details, popularity scores, links) and requirements (Spotify token, meaningful keywords). It doesn't mention rate limits, pagination, or error handling, but provides substantial behavioral context beyond basic functionality.

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 well-structured with clear sections (USE CASES, WHAT IT RETURNS, EXAMPLES, etc.) but is quite lengthy. Some sections like 'SEARCH STRATEGIES' could be more concise, and the front-loaded purpose statement is clear but followed by substantial detail that could be streamlined.

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?

For a search tool with 3 parameters, no annotations, and no output schema, the description provides comprehensive context including return values, use cases, examples, search strategies, and requirements. The main gap is lack of explicit output format details, but the 'WHAT IT RETURNS' section provides good semantic understanding.

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 description coverage is 67% (2 of 3 parameters have descriptions). The description compensates by providing extensive search strategies and examples that clarify how to use the 'query' parameter effectively. While it doesn't explicitly mention 'limit' parameter, the examples and strategies add significant semantic value beyond the schema.

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 tool searches for artists using names, genres, or keywords, with the specific purpose of discovering new music and talent. It distinguishes itself from sibling tools like 'search_albums', 'search_tracks', and 'get_artist' by focusing exclusively on artist search rather than other entity types or direct retrieval.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance through the 'USE CASES' section, listing five specific scenarios when to use this tool. It also distinguishes from alternatives by focusing on search rather than direct retrieval (e.g., 'get_artist' for known artists) and includes 'REQUIREMENTS' section specifying prerequisites like a valid Spotify access token.

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