Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_playlist

Retrieve Spotify playlist details by URI or ID, returning metadata and track items; omit both to use a default public playlist.

Instructions

Retrieve Spotify playlist details. Returns Spotify playlist metadata and items. Provide either uri or id; defaults to a known public playlist when omitted.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify playlist ID. Used when uri is omitted
uriNoSpotify playlist URI or open.spotify.com playlist URL
limitNoPlaylist item limit, clamped to 1-50
offsetNoPlaylist item offset
enable_watch_feed_entrypointNoEnable watch feed entrypoint
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return content and the default-resource fallback, which is real added context, but says nothing about pagination semantics, permissions/auth requirements, or rate limits despite exposing limit/offset parameters.

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?

Three tight sentences, front-loaded with purpose and each sentence carrying distinct information (what it does, what it returns, how to call it). No filler.

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

Completeness3/5

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

With no output schema it usefully states the return content, and it covers the id/uri input path. But for a 6-parameter tool it omits any treatment of limit/offset paging behavior and provides no differentiation from sibling playlist tools, leaving gaps.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying the either/or relationship between id and uri and by disclosing the fallback default when both are omitted—behavior not fully captured in the schema descriptions.

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?

States a specific verb+resource ('Retrieve Spotify playlist details') and clarifies the return payload ('metadata and items'). However, it never names or distinguishes itself from close siblings like spotify_playlists_search, spotify_profile_playlists, or spotify_artist_playlists, so the agent must infer the distinction from the name alone.

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

Usage Guidelines3/5

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

It gives the id-vs-uri selection rule and the default behavior when both are omitted, which is genuinely useful. But it offers no guidance on when to use this tool versus the sibling playlist/search tools, so usage context is only implied.

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