Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_me

Retrieve the authenticated user's Spotify profile details including display name, user ID, email, country, and subscription tier, with optional JSON output.

Instructions

Get the current user's Spotify profile: display name, user ID, email, country, and subscription level. Email requires the user-read-email scope; country and product require user-read-private.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.26.1
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/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 behavior disclosure. It goes beyond the schema by specifying the exact data fields returned and the auth scope prerequisites for certain fields, which is valuable context. It does not explicitly state read-only safety, but the 'Get' verb and profile-retrieval purpose make that reasonably clear.

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?

Two tight sentences: the first front-loads the tool's purpose and returned fields, and the second states scope requirements. There is no redundant wording, and all information is relevant to selecting and invoking the tool.

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

Completeness5/5

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

For a simple, zero-required-parameter read tool, the description is complete: it names the resource, enumerates the returned fields, and documents auth prerequisites. The input schema fully describes the only parameter, so nothing needed for correct invocation is missing.

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%, and the single parameter response_format is fully documented with an enum and a clear explanation of each value. The tool description adds no additional parameter meaning, but none is needed since the schema already carries the full weight.

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 states a specific verb ('Get') and resource ('current user's Spotify profile') and enumerates the exact fields returned: display name, user ID, email, country, and subscription level. This clearly distinguishes it from the many sibling tools covering artists, albums, playlists, and search.

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 description provides clear invocation context by stating the required OAuth scopes for specific fields: user-read-email for email and user-read-private for country and product. It does not explicitly name alternatives or exclusion cases, but the 'current user' phrasing strongly implies this is for the authenticated user's own profile rather than any other user.

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

Deploy Server

Other Tools