Skip to main content
Glama

get_album

Retrieve comprehensive album details from Spotify using the album ID, including track listings, artwork, release dates, and artist information for music discovery and playlist management.

Instructions

Retrieve comprehensive information about a specific album from Spotify using its unique identifier.

🎯 USE CASES: • Check album details before adding to playlist • Get track listing for a specific album • View album artwork, release date, and artist information • Research album metadata for music discovery

📝 WHAT IT RETURNS: • Album name, artists, and release date • Complete track listing with durations • Album artwork in multiple resolutions • Spotify popularity metrics and genre information • External URLs and market availability

🔍 EXAMPLES: • "Get details for the album 'Abbey Road' by The Beatles" • "Show me information about album ID: 1klALx0u4AavZNEvC4LrTL" • "I need the track list for this album I found"

⚠️ REQUIREMENTS: • Valid Spotify access token with appropriate scopes • Album must exist and be available in user's market

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesSpotify access token for authentication
albumIdYesSpotify album ID or URI

Implementation Reference

  • Primary registration of the 'get_album' MCP tool, defining title, description, input schema, and handler function
      get_album: {
        title: "Get Album",
        description: `Retrieve comprehensive information about a specific album from Spotify using its unique identifier.
    
    🎯 USE CASES:
    • Check album details before adding to playlist
    • Get track listing for a specific album
    • View album artwork, release date, and artist information
    • Research album metadata for music discovery
    
    📝 WHAT IT RETURNS:
    • Album name, artists, and release date
    • Complete track listing with durations
    • Album artwork in multiple resolutions
    • Spotify popularity metrics and genre information
    • External URLs and market availability
    
    🔍 EXAMPLES:
    • "Get details for the album 'Abbey Road' by The Beatles"
    • "Show me information about album ID: 1klALx0u4AavZNEvC4LrTL"
    • "I need the track list for this album I found"
    
    ⚠️ REQUIREMENTS:
    • Valid Spotify access token with appropriate scopes
    • Album must exist and be available in user's market`,
        schema: createSchema({
          token: commonSchemas.token(),
          albumId: commonSchemas.spotifyId("album"),
        }),
        handler: async (args: any, spotifyService: SpotifyService) => {
          const { token, albumId } = args;
          return await spotifyService.getAlbum(token, albumId);
        },
      },
  • The executable handler logic for the get_album tool, which parses arguments and delegates to SpotifyService
    handler: async (args: any, spotifyService: SpotifyService) => {
      const { token, albumId } = args;
      return await spotifyService.getAlbum(token, albumId);
    },
  • Input schema for get_album tool using common token and Spotify album ID validators
    schema: createSchema({
      token: commonSchemas.token(),
      albumId: commonSchemas.spotifyId("album"),
    }),
  • Core helper function in SpotifyService that fetches album data from Spotify API endpoint
    async getAlbum(token: string, albumId: string): Promise<SpotifyAlbum> {
      const id = this.extractId(albumId);
      return await this.makeRequest<SpotifyAlbum>(`albums/${id}`, token);
    }
  • Aggregation of all tools including albumTools (containing get_album) into central registry used by MCP server
    export const allTools: ToolsRegistry = {
      ...albumTools,
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 and does well by disclosing key behavioral traits: it specifies authentication requirements ('Valid Spotify access token with appropriate scopes'), market availability constraints ('Album must exist and be available in user's market'), and what the tool returns (detailed in 'WHAT IT RETURNS'). It does not mention rate limits or error handling, 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.

Conciseness4/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, REQUIREMENTS) and front-loaded with the core purpose. It is appropriately sized but could be slightly more concise by integrating some details (e.g., examples might be redundant with schema). Most sentences earn their place by adding context.

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, and requirements. However, it lacks explicit guidance on alternatives among siblings and does not detail output structure or error cases, which slightly limits completeness for an agent.

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 albumId). The description adds minimal value beyond this, mentioning the token in 'REQUIREMENTS' and albumId implicitly in examples, but no additional semantics like format details or usage tips. This meets the baseline of 3 when schema coverage is high.

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 ('retrieve comprehensive information') and resource ('specific album from Spotify'), and distinguishes it from sibling tools like get_album_tracks (which focuses only on tracks) and search_albums (which searches rather than retrieves a specific album). The title 'get_album' is accurately expanded in the description.

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 description provides clear context for when to use this tool through the 'USE CASES' section (e.g., checking album details, getting track listings). However, it does not explicitly state when NOT to use it or name alternatives among siblings (e.g., get_album_tracks for just tracks, search_albums for discovery), which prevents a perfect score.

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