Skip to main content
Glama
hrishi0102

Spotify MCP Server

by hrishi0102

get-current-user

Retrieve the current user's Spotify account details to manage playback, playlists, and preferences directly through the MCP server integration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler for get-current-user tool: fetches the current user's Spotify profile (/v1/me) using a valid access token and returns formatted user info (id, name, email, country) or error.
    server.tool("get-current-user", {}, async () => {
      try {
        const accessToken = await getValidAccessToken();
    
        const response = await fetch("https://api.spotify.com/v1/me", {
          headers: {
            Authorization: `Bearer ${accessToken}`,
          },
        });
    
        const data = (await response.json()) as any;
    
        if (!response.ok) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting user profile: ${JSON.stringify(data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  id: data.id,
                  name: data.display_name,
                  email: data.email,
                  country: data.country,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Failed to get user profile: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
          isError: true,
        };
      }
    });
  • Registers the get-current-user tool with empty input schema.
    server.tool("get-current-user", {}, async () => {
  • HTTP variant inline handler for get-current-user tool, similar to main but JS version with minor differences in error handling.
    server.tool("get-current-user", {}, async () => {
      try {
        const accessToken = await getValidAccessToken();
    
        const response = await fetch("https://api.spotify.com/v1/me", {
          headers: {
            Authorization: `Bearer ${accessToken}`,
          },
        });
    
        const data = await response.json();
    
        if (!response.ok) {
          return {
            content: [
              {
                type: "text",
                text: `Error getting user profile: ${JSON.stringify(data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                {
                  id: data.id,
                  name: data.display_name,
                  email: data.email,
                  country: data.country,
                },
                null,
                2
              ),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Failed to get user profile: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    });
  • OAuth HTTP variant handler using handleSpotifyTool helper, includes followers count, throws errors instead of returning isError.
    server.registerTool(
      "get-current-user",
      {
        title: "Get Current User",
        description: "Get current Spotify user information",
      },
      async () => {
        return await handleSpotifyTool(sessionId, async (accessToken) => {
          const response = await fetch("https://api.spotify.com/v1/me", {
            headers: {
              Authorization: `Bearer ${accessToken}`,
            },
          });
    
          const data = await response.json();
    
          if (!response.ok) {
            throw new Error(
              `Spotify API error: ${data.error?.message || "Unknown error"}`
            );
          }
    
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(
                  {
                    id: data.id,
                    name: data.display_name,
                    email: data.email,
                    country: data.country,
                    followers: data.followers?.total || 0,
                  },
                  null,
                  2
                ),
              },
            ],
          };
        });
      }
    );
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/hrishi0102/spotifyyy-mcp'

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