Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_profile_playlists

Fetch public Spotify playlists from a user profile via username, URI, or URL; defaults to Spotify's official profile.

Instructions

Retrieve Spotify public profile playlists. Returns public Spotify playlists. Provide username, uri, or url; defaults to Spotify's official profile.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify user URI
urlNoopen.spotify.com user URL
limitNoPlaylist limit, clamped to 1-50
offsetNoPlaylist offset
usernameNoSpotify username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations, so the description carries the full behavioral burden. It discloses that only public playlists are returned and that identity defaults to Spotify's official profile if nothing is supplied, which is genuine behavioral context. It omits pagination behavior, auth requirements, and rate limits, so gaps remain for an unannotated tool.

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

Conciseness3/5

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

Front-loads the core purpose in a single clear sentence, which is good. However, the second sentence ('Returns public Spotify playlists') is a near-verbatim restatement of the first and does not earn its place.

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 annotations and no output schema, the description should carry more of the behavioral and return-shape load. It covers identity selection and the default fallback adequately, but a 5-parameter, unannotated list tool with no pagination or auth context is only minimally complete.

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 username/uri/url/limit/offset are already documented in the schema, setting the baseline at 3. The description adds the useful fact that the three identity parameters are interchangeable, but says nothing about limit/offset semantics beyond the schema.

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 (Retrieve) and resource (Spotify public profile playlists), and the scope 'public profile' distinguishes it from spotify_artist_playlists and spotify_playlists_search. However, the second sentence ('Returns public Spotify playlists') simply restates the first rather than adding differentiation, so it stops short of the 5-level sibling routing.

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 one piece of actionable guidance: 'Provide username, uri, or url; defaults to Spotify's official profile,' which tells the agent the alternative identifiers and the fallback behavior. But there is no explicit when-to-use versus siblings like spotify_profile or spotify_profile_followers, leaving the choice 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