Skip to main content
Glama

get_new_releases

Discover recently released albums on Spotify to stay current with new music, find genre-specific releases, and build updated playlists.

Instructions

Discover the latest album releases available on Spotify, perfect for staying up-to-date with new music.

🎯 USE CASES: • Weekly music discovery sessions • Finding new releases from favorite genres • Building "New Music Friday" playlists • Keeping up with trending releases in specific regions • Music blog content creation and curation

📝 WHAT IT RETURNS: • Recently released albums with release dates • Artist information and album artwork • Spotify popularity scores and listener counts • Genre classifications and market availability • External links and preview URLs where available

🔍 EXAMPLES: • "Show me the latest album releases this week" • "What new albums came out in the UK recently?" • "Find new releases, limit to 10 albums" • "I want to discover new music that just dropped"

💡 TIPS: • Use country parameter to get region-specific releases • Adjust limit based on how many discoveries you want • Perfect for automated weekly new music updates

⚠️ REQUIREMENTS: • Valid Spotify access token • Optional: Country code for region-specific results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesSpotify access token for authentication
limitNo
countryNoCountry code for localized content (e.g., 'US', 'GB')

Implementation Reference

  • The MCP tool handler for 'get_new_releases'. It parses arguments (token, limit, country) and delegates execution to the SpotifyService.getNewReleases method.
    handler: async (args: any, spotifyService: SpotifyService) => {
      const { token, limit = 20, country } = args;
      return await spotifyService.getNewReleases(token, limit, country);
    },
  • The input schema definition for the 'get_new_releases' tool, specifying parameters: token (required), limit (1-50, default 20), country (optional).
    schema: createSchema({
      token: commonSchemas.token(),
      limit: commonSchemas.limit(1, 50, 20),
      country: commonSchemas.country(),
    }),
  • The albumTools object (containing 'get_new_releases') is included in the central allTools registry via object spread. This registry is used by ToolRegistrar for MCP tool listing and execution.
    ...albumTools,
  • The SpotifyService helper method implementing the core logic: calls Spotify API endpoint 'browse/new-releases' with limit and optional country parameters, returning paging object of new albums.
    async getNewReleases(
      token: string,
      limit: number = 20,
      country: string | null = null
    ): Promise<{ albums: PagingObject<SpotifyAlbum> }> {
      const params: Record<string, any> = { limit: Math.min(limit, 50) };
      if (country) params.country = country;
      return await this.makeRequest<{ albums: PagingObject<SpotifyAlbum> }>(
        "browse/new-releases",
        token,
        params
      );
    }
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 discloses key behaviors: authentication requirement ('Valid Spotify access token'), regional filtering capability, and return content details (e.g., popularity scores, preview URLs). However, it lacks explicit rate limit or pagination information, though the limit parameter hints at constraints.

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, etc.), but it is verbose. Some content (e.g., detailed return items) could be condensed, and the front-loaded purpose statement is followed by extensive lists rather than prioritized information.

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 and no output schema, the description provides comprehensive context: purpose, usage, parameters, returns, and requirements. It covers authentication, regionalization, and output details adequately. However, it lacks explicit error handling or rate limit information, which would enhance completeness for a 3-param tool.

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 described). The description adds value beyond the schema: it explains the purpose of the country parameter ('region-specific releases'), provides context for limit ('how many discoveries you want'), and clarifies token usage ('Spotify access token for authentication'). It doesn't fully compensate for the missing limit description but adds meaningful semantics.

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: 'Discover the latest album releases available on Spotify.' It specifies the resource (albums) and verb (discover latest releases), and distinguishes it from siblings like get_album (single album) or search_albums (search query-based).

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 dedicated sections: 'USE CASES' lists specific scenarios (e.g., weekly discovery, region-specific updates), 'EXAMPLES' shows query patterns, and 'TIPS' advises on parameter usage (country, limit). It implicitly distinguishes from siblings by focusing on new releases rather than search or existing content.

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