Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

createPlaylist

Create a new Spotify playlist with a name, optional description, and privacy settings to organize your music collection.

Instructions

Create a new playlist on Spotify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the playlist
descriptionNoThe description of the playlist
publicNoWhether the playlist should be public

Implementation Reference

  • The handler function for the 'createPlaylist' tool. It destructures args, gets the current user profile, creates the playlist using spotifyApi.playlists.createPlaylist, and returns a success message with the playlist ID.
    handler: async (args, _extra: SpotifyHandlerExtra) => {
      const { name, description, public: isPublic = false } = args;
    
      const result = await handleSpotifyRequest(async (spotifyApi) => {
        const me = await spotifyApi.currentUser.profile();
    
        return await spotifyApi.playlists.createPlaylist(me.id, {
          name,
          description,
          public: isPublic,
        });
      });
    
      return {
        content: [
          {
            type: 'text',
            text: `Successfully created playlist "${name}"\nPlaylist ID: ${result.id}`,
          },
        ],
      };
    },
  • Zod input schema for the 'createPlaylist' tool defining required 'name' string, optional 'description' string, and optional 'public' boolean.
    schema: {
      name: z.string().describe('The name of the playlist'),
      description: z
        .string()
        .optional()
        .describe('The description of the playlist'),
      public: z
        .boolean()
        .optional()
        .describe('Whether the playlist should be public'),
    },
  • src/index.ts:12-14 (registration)
    Main MCP server registration loop that registers the 'createPlaylist' tool (via playTools) by calling server.tool with its name, description, schema, and handler.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
  • src/play.ts:362-371 (registration)
    Local grouping of play-related tools including 'createPlaylist' in the exported playTools array, which is then registered in index.ts.
    export const playTools = [
      playMusic,
      pausePlayback,
      skipToNext,
      skipToPrevious,
      createPlaylist,
      addTracksToPlaylist,
      resumePlayback,
      addToQueue,
    ];
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. While 'Create' implies a write operation, it doesn't specify authentication requirements, rate limits, whether the playlist is created for the current user or another user, or what happens on success/failure. This is inadequate for a mutation tool with zero annotation coverage.

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 communicates the core purpose without any wasted words. It's appropriately sized and front-loaded with the essential information.

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 insufficient. It doesn't explain what happens after creation (e.g., returns a playlist ID), authentication requirements, or error conditions. Given the complexity of creating a resource in an external API, more context is needed.

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 schema description coverage is 100%, with all three parameters clearly documented in the schema itself. The description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 for adequate coverage when the schema does the heavy lifting.

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 ('Create') and resource ('new playlist on Spotify'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'getMyPlaylists' or 'addTracksToPlaylist' beyond the obvious creation vs. retrieval 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. It doesn't mention prerequisites (like authentication), when not to use it, or how it relates to sibling tools like 'addTracksToPlaylist' for modifying existing playlists.

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