@striderlabs/mcp-spotify

get_playlists

Retrieve all Spotify playlists from your library, including owned and followed. Returns playlist names, IDs, and URIs for easy management.

Instructions

Get all playlists in your Spotify library (owned and followed). Returns playlist names, IDs, and URIs.

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": "get_playlists"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of playlists to return (1-50, default: 50)

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?

The description clearly states the action (get) and the return fields. It says 'all playlists' but the limit parameter suggests a maximum, which is discussed. No annotations provided, but the description is transparent about what is returned.

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

Conciseness4/5

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

The description is concise and to the point, but could be structured with more details on the return format or pagination. However, it's not overly verbose.

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?

The description mentions it's for the user's library surfaces, but doesn't specify authentication or error responses. However, schema provides a parameter.

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

Parameters5/5

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

There is one parameter, limit, with a clear description including range and default value. No ambiguity.

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 what the tool does (gets all playlists in the user's Spotify library) and exactly what it returns (names, IDs, and URIs). The scope is explicitly defined as 'owned and followed' playlists, leaving no ambiguity about the purpose.

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 specifies the content (owned and followed playlists) and the parameter, but does not mention authentication requirements or typical usage patterns. However, given the context of sibling tools like spotify_auth, it's implied. It could be more explicit about the need for prior authentication.

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