Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_user_playlists

Read-onlyIdempotent

List the current user's Spotify playlists with options for pagination and result limits. Fetches up to 500 playlists or a specified number for efficient management.

Instructions

List the current user's playlists

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo1–50. Default: 20
offsetNoPagination offset. Default: 0
fetch_allNoFetch every playlist (up to 500), continuing FROM offset rather than restarting at 0. limit is the page size. Note: library tools' fetch_all instead ignores offset — contracts differ between modules (#110).
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed5 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / fetch_all / description
      Previous value: -"Fetch every page (up to 500 playlists) instead of a single page"New value: +"Fetch every playlist (up to 500), continuing FROM offset rather than restarting at 0. limit is the page size. Note: library tools' fetch_all instead ignores offset — contracts differ between modules (#110)."
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
    • 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"
+}
  3. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered by structured data; 'List' is consistent with these hints. The description adds no behavioral context beyond what annotations imply, but with annotations present the bar is lower and no contradiction exists. It contributes little extra, warranting a mid score.

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?

A single clean sentence with no filler, appropriately short for a straightforward read operation whose safety is already flagged by annotations. It is front-loaded with the verb and target. Slightly more utility could be packed in, but the brevity is justified here.

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 rich parameter descriptions in the schema and annotations covering read-only/idempotent safety, the description is largely complete for a simple list tool. The main gap is the absence of an output schema and no description-level note about return shape, but for a basic current-user playlist listing this is a minor omission.

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%, so the baseline is 3 even with no parameter info in the description. The schema itself carries detailed semantics, including fetch_all's notable contract difference versus library tools and response_format's prose-versus-JSON modes. The description adds nothing on top, but the schema does the heavy lifting.

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 states a clear verb ('List') and resource ('the current user's playlists'). It implicitly distinguishes itself from the sibling get_user_playlists_by_id by scoping to the current user rather than an arbitrary user ID. Brief but specific enough to identify the operation at a glance.

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?

No guidance on when to use this tool versus alternatives. The natural sibling get_user_playlists_by_id exists for listing another user's playlists, but the description never mentions it or the condition that selects between them. There is also no note about the several pagination/response-format parameters that control behavior, leaving routing and configuration choices entirely to inference.

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