Skip to main content
Glama
superseoworld

MCP Spotify Server

get_new_releases

Retrieve recently added albums from Spotify's catalog to discover fresh music content.

Instructions

Get a list of new album releases featured in Spotify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoOptional. A country code (ISO 3166-1 alpha-2)
limitNoMaximum number of releases to return (1-50)
offsetNoThe index of the first release to return

Implementation Reference

  • Implements the core logic for fetching new album releases from Spotify's /browse/new-releases endpoint, including parameter validation and API request.
    async getNewReleases(args: NewReleasesArgs) {
      const { country, limit = 20, offset = 0 } = args;
    
      if (limit < 1 || limit > 50) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Limit must be between 1 and 50'
        );
      }
    
      if (offset < 0) {
        throw new McpError(
          ErrorCode.InvalidParams,
          'Offset must be non-negative'
        );
      }
    
      const params = {
        country,
        limit,
        offset
      };
    
      return this.api.makeRequest(
        `/browse/new-releases${this.api.buildQueryString(params)}`
      );
    }
  • TypeScript interface defining the input arguments for the getNewReleases tool, extending PaginationParams with optional country.
    export interface NewReleasesArgs extends PaginationParams {
      country?: string;
    }
  • src/index.ts:319-343 (registration)
    Registers the get_new_releases tool in the MCP server's listTools response, including name, description, and input schema.
      name: 'get_new_releases',
      description: 'Get a list of new album releases featured in Spotify',
      inputSchema: {
        type: 'object',
        properties: {
          country: {
            type: 'string',
            description: 'Optional. A country code (ISO 3166-1 alpha-2)'
          },
          limit: {
            type: 'number',
            description: 'Maximum number of releases to return (1-50)',
            minimum: 1,
            maximum: 50,
            default: 20
          },
          offset: {
            type: 'number',
            description: 'The index of the first release to return',
            minimum: 0,
            default: 0
          }
        }
      },
    },
  • src/index.ts:789-795 (registration)
    Dispatches calls to the get_new_releases tool by invoking the AlbumsHandler's getNewReleases method with validated arguments.
    case 'get_new_releases': {
      const args = this.validateArgs<NewReleasesArgs>(request.params.arguments || {}, []);
      const result = await this.albumsHandler.getNewReleases(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 the full burden of behavioral disclosure. It states what the tool does but lacks critical details such as whether this is a read-only operation, potential rate limits, authentication requirements, or what the output format looks like (e.g., list structure, pagination). This leaves significant gaps for an agent to understand how to interact with it effectively.

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 directly states the tool's purpose without any unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

Given the complexity of a list-retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral traits like pagination or authentication needs, which are essential for an agent to use this tool correctly in a real-world context.

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, providing clear details on all three parameters (country, limit, offset). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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') and resource ('new album releases featured in Spotify'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from siblings like 'get_album' or 'get_featured_playlists', which might also retrieve album-related content, so it misses full sibling distinction.

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. For example, it doesn't clarify if this is for browsing new releases versus searching for specific albums or getting playlist-based recommendations, leaving the agent to infer usage from context alone.

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