Skip to main content
Glama

get_artist

Retrieve detailed artist information from Spotify including biography, genres, popularity metrics, and related artists for music research and discovery.

Instructions

Get comprehensive information about any artist including their biography, genres, and popularity metrics.

🎯 USE CASES: • Research artist background before concerts or festivals • Build artist-focused playlists with complete discography knowledge • Discover artist genres and influences for music recommendations • Analyze artist popularity trends and follower growth • Create detailed artist profiles for music databases

📝 WHAT IT RETURNS: • Artist name, biography, and profile images • Genre classifications and musical styles • Spotify popularity score and follower count • External URLs (official website, social media) • Related artist suggestions and collaborators

🔍 EXAMPLES: • "Get information about Taylor Swift" • "Show me details for artist ID: 06HL4z0CvFAxyc27GXpf02" • "I want to learn about this new artist I discovered" • "Get profile info for the band that sang this song"

💡 TIPS: • Use before exploring an artist's full catalog • Great for understanding an artist's evolution over time • Check follower count to gauge current popularity

⚠️ REQUIREMENTS: • Valid Spotify access token • Artist must exist in Spotify's database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesSpotify access token for authentication
artistIdYesSpotify artist ID or URI

Implementation Reference

  • The handler function that executes the get_artist tool logic, delegating to SpotifyService.getArtist
    handler: async (args: any, spotifyService: SpotifyService) => {
      const { token, artistId } = args;
      return await spotifyService.getArtist(token, artistId);
    },
  • Input schema for the get_artist tool, defining required token and artistId parameters
    schema: createSchema({
      token: commonSchemas.token(),
      artistId: commonSchemas.spotifyId("artist"),
    }),
  • SpotifyService.getArtist helper method that performs the actual API request to Spotify for artist data
    async getArtist(token: string, artistId: string): Promise<SpotifyArtist> {
      const id = this.extractId(artistId);
      return await this.makeRequest<SpotifyArtist>(`artists/${id}`, token);
    }
  • Registration of artistTools (including get_artist) into the central allTools registry used by ToolRegistrar
    export const allTools: ToolsRegistry = {
      ...albumTools,
    
      ...artistTools,
    
      ...trackTools,
    
      ...playlistTools,
    
      ...playbackTools,
    
      ...userTools,
    
      ...searchTools,
    };
  • Instantiation of ToolRegistrar in MCP server, which registers all tools including get_artist for MCP usage
    const toolRegistrar = new ToolRegistrar(spotifyService);
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 of behavioral disclosure. It effectively describes what the tool returns (e.g., 'Artist name, biography, profile images'), includes authentication needs ('Valid Spotify access token'), and hints at data source constraints ('Artist must exist in Spotify's database'). However, it lacks details on rate limits, error handling, or pagination, which are minor gaps.

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 well-structured with clear sections (e.g., 'USE CASES', 'WHAT IT RETURNS'), front-loaded with the core purpose, and every sentence adds value without redundancy. It efficiently conveys information in a readable format, making it easy for an agent to parse.

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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is largely complete. It covers purpose, usage, returns, examples, tips, and requirements. However, without an output schema, it could benefit from more detail on the return structure (e.g., data types), but the 'WHAT IT RETURNS' section mitigates this gap adequately.

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?

The input schema has 100% description coverage, clearly documenting both parameters ('token' and 'artistId'). The description does not add significant semantic details beyond what the schema provides, such as format examples for 'artistId' or token usage nuances. Thus, it meets the baseline of 3, as the schema does the heavy lifting.

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's purpose with specific verbs ('Get comprehensive information') and resources ('about any artist'), distinguishing it from siblings like 'search_artists' (which searches) or 'get_artist_albums' (which focuses on albums). It explicitly lists what information is retrieved, making the purpose unambiguous.

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 sections like 'USE CASES' (e.g., 'Research artist background before concerts') and 'TIPS' (e.g., 'Use before exploring an artist's full catalog'), which help differentiate when to use this tool versus alternatives like 'search_artists' for discovery or 'get_artist_top_tracks' for specific content. It also includes 'REQUIREMENTS' that specify prerequisites.

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