Skip to main content
Glama
makesh-kumar

Spotify MCP Server

by makesh-kumar

getNowPlaying

Retrieve details about the song currently playing on Spotify, including track name, artist, and album information.

Instructions

Get information about the currently playing track on Spotify

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full implementation of the getNowPlaying tool, including empty schema and the handler function that fetches the currently playing Spotify track, validates it, formats artist, album, progress, duration, and ID into a markdown 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?.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/index.ts:12-14 (registration)
    Registers the getNowPlaying tool (via readTools array) with the MCP server by calling server.tool() for each tool in the combined arrays.
    [...readTools, ...playTools, ...albumTools].forEach((tool) => {
      server.tool(tool.name, tool.description, tool.schema, tool.handler);
    });
  • src/read.ts:531-539 (registration)
    Exports the readTools array containing the getNowPlaying tool for registration in the main index file.
    export const readTools = [
      searchSpotify,
      getNowPlaying,
      getMyPlaylists,
      getPlaylistTracks,
      getRecentlyPlayed,
      getUsersSavedTracks,
      getQueue,
    ];
  • Helper function used by the 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'
      );
    }
  • Empty schema indicating the tool takes no input parameters.
    schema: {},
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. It mentions retrieving information, implying a read-only operation, but doesn't specify authentication needs, rate limits, error conditions, or what happens if no track is playing. This leaves significant gaps for an agent to understand the tool's behavior.

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 states the tool's purpose without any unnecessary words. It's front-loaded and efficiently communicates the core functionality, making it easy for an agent 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?

Given the tool's moderate complexity (retrieving real-time playback data) and the lack of annotations and output schema, the description is insufficient. It doesn't explain what information is returned (e.g., track details, playback state), error handling, or dependencies like active playback, leaving the agent with incomplete 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 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist.

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 ('Get information about') and the resource ('currently playing track on Spotify'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'getQueue' or 'getRecentlyPlayed', which also retrieve playback information, so it doesn't reach the highest score.

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 'getQueue' or 'getRecentlyPlayed', nor does it mention prerequisites such as requiring active playback. It simply states what the tool does without context for selection.

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