Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

addTracksToPlaylist

Add multiple songs to a specific Spotify playlist using track IDs, optionally specifying insertion position.

Instructions

Add tracks to a Spotify playlist

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playlistIdYesThe Spotify ID of the playlist
trackIdsYesArray of Spotify track IDs to add
positionNoPosition to insert the tracks (0-based index)

Implementation Reference

  • Handler function that destructures args, validates trackIds array, converts IDs to URIs, calls Spotify API to add items to playlist at optional position, handles errors, and returns formatted content response.
    handler: async (args, _extra: SpotifyHandlerExtra) => {
      const { playlistId, trackIds, position } = args;
    
      if (trackIds.length === 0) {
        return {
          content: [
            {
              type: 'text',
              text: 'Error: No track IDs provided',
            },
          ],
        };
      }
    
      try {
        const trackUris = trackIds.map((id) => `spotify:track:${id}`);
    
        await handleSpotifyRequest(async (spotifyApi) => {
          await spotifyApi.playlists.addItemsToPlaylist(
            playlistId,
            trackUris,
            position,
          );
        });
    
        return {
          content: [
            {
              type: 'text',
              text: `Successfully added ${trackIds.length} track${
                trackIds.length === 1 ? '' : 's'
              } to playlist (ID: ${playlistId})`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error adding tracks to playlist: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    },
  • Zod schema defining the input parameters: required playlistId (string), trackIds (array of strings), optional position (non-negative number).
    schema: {
      playlistId: z.string().describe('The Spotify ID of the playlist'),
      trackIds: z.array(z.string()).describe('Array of Spotify track IDs to add'),
      position: z
        .number()
        .nonnegative()
        .optional()
        .describe('Position to insert the tracks (0-based index)'),
    },
  • src/play.ts:362-371 (registration)
    addTracksToPlaylist tool is included in the exported playTools array.
    export const playTools = [
      playMusic,
      pausePlayback,
      skipToNext,
      skipToPrevious,
      createPlaylist,
      addTracksToPlaylist,
      resumePlayback,
      addToQueue,
    ];
  • src/index.ts:12-14 (registration)
    playTools (containing addTracksToPlaylist) imported and registered to 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool adds tracks, implying a write operation, but doesn't mention permissions (e.g., user must own or follow the playlist), rate limits, or what happens on failure (e.g., partial additions). This leaves significant gaps for a mutation tool.

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 front-loaded and wastes no words, making it easy 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?

For a mutation tool with no annotations and no output schema, the description is inadequate. It doesn't cover behavioral aspects like authentication needs, error handling, or return values, leaving the agent with insufficient context to use the tool effectively beyond basic parameter mapping.

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 all parameters (playlistId, trackIds, position). The description adds no additional meaning beyond the schema, such as explaining track ID formats or position behavior. With high schema coverage, the baseline score of 3 is appropriate.

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 ('Add tracks') and target resource ('to a Spotify playlist'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'addToQueue' or 'playMusic', which also involve adding or playing tracks in different contexts.

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 like 'addToQueue' (for immediate playback) or 'createPlaylist' (for making new playlists). It lacks context about prerequisites, such as needing an existing playlist, or exclusions, like not being suitable for modifying track order beyond insertion.

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