@striderlabs/mcp-spotify

spotify_auth

Authenticate with Spotify via OAuth 2.0 PKCE. Opens a browser for authorization. Use once to store tokens locally, enabling other Spotify tools to access your account.

Instructions

Authenticate with Spotify using OAuth 2.0 with PKCE. Opens a browser window for you to authorize access. Requires SPOTIFY_CLIENT_ID environment variable. Only needed once — tokens are stored locally.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_auth"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A4.4/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. It discloses key behaviors: opens a browser window, requires user authorization, and stores tokens locally. It also notes the tool is only needed once, implying idempotence. It does not mention potential delays or failure modes, but for this simple auth tool, it is sufficiently transparent.

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 two sentences, immediately front-loading the purpose and then adding essential details (browser, env var, one-time need). Every word earns its place; no fluff.

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

Completeness4/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 params, no output schema), the description is largely complete. It covers what, how, and prerequisites. It could briefly link to sibling tools (e.g., 'after this, you can use Spotify search and playback tools'), but that is a minor gap. The mention of local token storage implies persistence.

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, so the input schema is trivially complete. The description adds context about the OAuth flow and environment variable, which is useful but not strictly parameter-related. Baseline for 0 params is 4, and this description meets it without exceeding.

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 tool authenticates with Spotify using OAuth 2.0 with PKCE and opens a browser for authorization. It is distinct from all siblings, which focus on music actions, and specifies the resource (Spotify) and action (authenticate).

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 implies this is a prerequisite for other Spotify tools by stating 'Only needed once — tokens are stored locally.' It also mentions the required SPOTIFY_CLIENT_ID environment variable. However, it does not explicitly say 'use this before other Spotify tools if not authenticated,' but the context makes that obvious.

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