Skip to main content
Glama
igorgarbuz

Spotify MCP Node Server

by igorgarbuz

getNowPlaying

Retrieve details of the currently playing Spotify track, including title, artist, and album information.

Instructions

Get information about the currently playing track on Spotify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full tool definition including name, description, empty schema (no inputs), and handler function. The handler fetches the currently playing track using Spotify API, validates it's a track, formats artist, album, progress, duration, and returns formatted text response.
    const getNowPlaying: tool<Record<string, never>> = {
      name: 'getNowPlaying',
      description: 'Get information about the currently playing track on Spotify',
      schema: {},
      handler: async (args, extra: SpotifyHandlerExtra) => {
        try {
          const currentTrack = await handleSpotifyRequest(async (spotifyApi) => {
            return await spotifyApi.player.getCurrentlyPlayingTrack();
          });
    
          if (!currentTrack || !currentTrack.item) {
            return {
              content: [
                {
                  type: 'text',
                  text: 'Nothing is currently playing on Spotify',
                },
              ],
            };
          }
    
          const item = currentTrack.item;
    
          if (!isTrack(item)) {
            return {
              content: [
                {
                  type: 'text',
                  text: 'Currently playing item is not a track (might be a podcast episode)',
                },
              ],
            };
          }
    
          const artists = item.artists.map((a) => a.name).join(', ');
          const album = item.album.name;
          const duration = formatDuration(item.duration_ms);
          const progress = formatDuration(currentTrack.progress_ms || 0);
          const isPlaying = currentTrack.is_playing;
    
          return {
            content: [
              {
                type: 'text',
                text:
                  `# Currently ${isPlaying ? 'Playing' : 'Paused'}\n\n` +
                  `**Track**: "${item.name}"\n` +
                  `**Artist**: ${artists}\n` +
                  `**Album**: ${album}\n` +
                  `**Progress**: ${progress} / ${duration}\n` +
                  `**ID**: ${item.id}`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `Error getting current track: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      },
    };
  • src/read.ts:521-529 (registration)
    getNowPlaying is included in the readTools array which groups read-related tools.
    export const readTools = [
      searchSpotify,
      getNowPlaying,
      getUserPlaylists,
      getPlaylistTracks,
      getRecentlyPlayed,
      getFollowedArtists,
      getUserTopItems,
    ];
  • src/index.ts:12-14 (registration)
    All tools from playTools, readTools, writeTools are registered on the MCP server using server.tool() in a loop.
    [...playTools, ...readTools, ...writeTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
  • Helper function used in getNowPlaying handler to validate if the playing item is a track.
    function isTrack(item: any): item is SpotifyTrack {
      return (
        item &&
        item.type === 'track' &&
        Array.isArray(item.artists) &&
        item.album &&
        typeof item.album.name === 'string'
      );
    }
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 but offers minimal insight. It states what the tool does ('Get information') but doesn't describe response format, error conditions, authentication requirements, rate limits, or whether it requires an active playback session. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves in practice.

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, clear sentence that directly communicates the tool's function without any fluff or redundancy. It's front-loaded with the core purpose ('Get information about the currently playing track') and specifies the context ('on Spotify'). Every word earns its place, making it highly efficient for an agent to parse.

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 simplicity (no parameters, no annotations, no output schema), the description is minimally adequate. It states what the tool does but lacks details on return values, error handling, or dependencies like active playback. For a read operation that likely returns structured data, the absence of output schema means the description should ideally hint at response format, but it doesn't—leaving the agent with incomplete operational context.

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 tool has zero parameters, and schema description coverage is 100% (empty schema is fully documented). The description appropriately doesn't discuss parameters since none exist, avoiding unnecessary detail. It focuses solely on the tool's purpose, which is sufficient given the parameterless design.

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 tool's purpose with a specific verb ('Get information') and resource ('currently playing track on Spotify'), making it immediately understandable. It doesn't explicitly distinguish from siblings like 'getRecentlyPlayed' or 'getUserTopItems', but the focus on 'currently playing' provides inherent differentiation. The description avoids tautology by specifying what information is retrieved rather than just restating the name.

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 (e.g., requiring active Spotify playback), exclusions, or comparisons to sibling tools like 'getRecentlyPlayed' for historical data or 'playbackAction' for control operations. The agent must infer usage context solely from the tool name and description without explicit direction.

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