Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

saveOrRemoveAlbumForUser

Add or delete albums from your Spotify "Your Music" library. Manage your saved albums by specifying album IDs and choosing save or remove actions.

Instructions

Save or remove albums from the user's "Your Music" library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
albumIdsYesArray of Spotify album IDs (max 20)
actionYesAction to perform: save or remove albums

Implementation Reference

  • The async handler function that destructures args, validates albumIds, calls Spotify API to save or remove albums based on action, and returns success or error messages.
      handler: async (args, _extra: SpotifyHandlerExtra) => {
        const { albumIds, action } = args;
    
        if (albumIds.length === 0) {
          return {
            content: [
              {
                type: 'text',
                text: 'Error: No album IDs provided',
              },
            ],
          };
        }
    
        try {
          await handleSpotifyRequest(async (spotifyApi) => {
            return action === 'save'
              ? await spotifyApi.currentUser.albums.saveAlbums(albumIds)
              : await spotifyApi.currentUser.albums.removeSavedAlbums(albumIds);
          });
    
          const actionPastTense = action === 'save' ? 'saved' : 'removed';
          const preposition = action === 'save' ? 'to' : 'from';
    
          return {
            content: [
              {
                type: 'text',
                text: `Successfully ${actionPastTense} ${albumIds.length} album${albumIds.length === 1 ? '' : 's'} ${preposition} your library`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error ${action === 'save' ? 'saving' : 'removing'} albums: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      },
    };
  • Zod schema validating the input parameters: albumIds as array of strings (max 20) and action as 'save' or 'remove'.
    schema: {
      albumIds: z
        .array(z.string())
        .max(20)
        .describe('Array of Spotify album IDs (max 20)'),
      action: z
        .enum(['save', 'remove'])
        .describe('Action to perform: save or remove albums'),
    },
  • src/albums.ts:299-304 (registration)
    Local registration of the tool in the albumTools array which is exported for use in main index.
    export const albumTools = [
      getAlbums,
      getAlbumTracks,
      saveOrRemoveAlbumForUser,
      checkUsersSavedAlbums,
    ];
  • src/index.ts:12-14 (registration)
    Global registration where all tools including albumTools are registered to the MCP server via server.tool() calls.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
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 mentions the action (save/remove) but doesn't disclose critical traits like authentication requirements, rate limits, whether changes are permanent, or what happens if album IDs are invalid. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 fluff. It's appropriately sized and front-loaded, with every word contributing to understanding the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 (a mutation operation with two parameters), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavioral traits, error handling, or return values, which are important for a tool that modifies user data.

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?

The input schema has 100% description coverage, so the schema already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, but with zero parameters left undocumented, the baseline is high. A score of 4 reflects that the description doesn't compensate for any gaps (since there are none), but also doesn't add extra value.

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 specific action ('save or remove'), the resource ('albums'), and the target location ("user's 'Your Music' library"). It precisely distinguishes this tool from siblings like 'checkUsersSavedAlbums' (which only checks) or 'addTracksToPlaylist' (which targets playlists rather than the user's library).

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

Usage Guidelines3/5

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

The description implies usage for managing albums in the user's personal library, but it doesn't explicitly state when to use this tool versus alternatives like 'addTracksToPlaylist' or 'createPlaylist'. It provides basic context (managing 'Your Music' library) but lacks explicit exclusions or comparisons with sibling tools.

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/makesh-kumar/spotify-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server