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'
      );
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the burden of behavioral disclosure. It implies a read-only operation via 'Get', but does not explicitly state that it has no side effects, requires active playback, or what happens if nothing is playing. The description adds minimal behavioral context beyond the tool's basic function.

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, concise sentence that conveys the essential purpose without any fluff or redundancy. Every word earns its place, and the information density is high.

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?

The tool is simple (no parameters, no output schema), but the description is somewhat thin. It does not specify what 'information' is returned (e.g., track name, artist, album) or address edge cases like no active playback. For a simple read tool, this is moderately complete but leaves room for ambiguity.

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 zero parameters, and the description correctly avoids inventing any. With no parameters, the schema coverage is effectively 100%, and the baseline of 4 applies. The description does not need to add parameter-level detail.

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 verb 'Get' and the resource 'currently playing track on Spotify', which directly and unambiguously describes the tool's purpose. It is distinct from sibling tools like getRecentlyPlayed or searchSpotify, as it specifically targets the current playback state.

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

Usage Guidelines4/5

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

The phrase 'currently playing' provides clear context that this tool is for retrieving live playback information, implicitly distinguishing it from search or playlist retrieval. However, it does not explicitly mention when not to use it or reference alternative tools, falling short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.