Skip to main content
Glama
igorgarbuz

Spotify MCP Node Server

by igorgarbuz

createPlaylist

Create a new playlist on Spotify by specifying its name, description, and privacy settings. This tool enables AI assistants to organize music collections directly through the Spotify MCP Node Server.

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 that creates a Spotify playlist for the current user using the provided name, optional description, and public flag. It uses handleSpotifyRequest utility and returns success message with 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}`,
          },
        ],
      };
    },
  • Tool name, description, and Zod input schema defining required 'name' (string) and optional 'description' (string), 'public' (boolean).
    name: 'createPlaylist',
    description: 'Create a new playlist on Spotify',
    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/write.ts:238-243 (registration)
    The createPlaylist tool is included in the exported writeTools array alongside other write operations.
    export const writeTools = [
      addToQueue,
      addTracksToPlaylist,
      createPlaylist,
      removeTracksFromPlaylist,
    ];
  • src/index.ts:12-14 (registration)
    All tools from playTools, readTools, and writeTools (including createPlaylist) are registered with the MCP server by calling server.tool() for each.
    [...playTools, ...readTools, ...writeTools].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 full burden for behavioral disclosure. It states the tool creates a playlist but doesn't mention what permissions are needed, whether this requires user authentication, what happens on success/failure, or any rate limits. For a write operation with zero annotation coverage, this leaves significant gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple creation tool and front-loads 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 write operation with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., returns playlist ID), what authentication is required, or potential error conditions. Given the complexity of creating a resource in an external service, 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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. Baseline 3 is appropriate when the schema does the heavy lifting for parameter documentation.

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 'addTracksToPlaylist' or 'getUserPlaylists' beyond the creation aspect.

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. There's no mention of prerequisites (like authentication), when not to use it, or how it differs from related 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/igorgarbuz/spotify-mcp'

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