Crawlora MCP

spotify_profile_playlists

Read-only

Fetch public playlists for a Spotify profile by username, uri, or url; limit/offset paginate, and the official Spotify profile is the default. Use spotify_profile for profile details, spotify_artist_playlists for artist playlists, or spotify_playlists_search for playlist search.

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_profile_playlists"
  }
}

Input Schema

Name	Required	Description
`uri`	No	Spotify user URI, e.g. spotify:user:spotify; provide one of username, uri, or url.
`url`	No	Open Spotify user URL, e.g. https://open.spotify.com/user/spotify; provide one of username, uri, or url.
`limit`	No	Playlist limit, clamped to 1-50.
`offset`	No	Playlist offset, default 0.
`username`	No	Spotify username, e.g. spotify; provide one of username, uri, or url.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful beyond-annotation context: results are limited to PUBLIC playlists, the official Spotify profile is the default when no identifier is given, and limit/offset drive pagination. Permission/rate-limit behavior is not mentioned, keeping this from a 5.

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?

Two sentences, zero waste, with the core action and identifier options front-loaded before the disambiguation guidance. Every clause earns its place.

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?

With an output schema present, return values need not be explained, and the description covers identification, pagination, default behavior, and sibling routing. It is nearly complete for a read-only list tool; only edge cases like invalid identifiers are unaddressed.

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% and the schema already states the one-of username/uri/url constraint and the limit/offset semantics, so the description largely restates structured data. Baseline 3 is appropriate; it adds only light reinforcement of the pagination and default-identifier behavior.

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?

States a specific verb (Fetch) and resource (public playlists for a Spotify profile) and enumerates the three identifier forms accepted. It also names the sibling tools it is not, so an agent can distinguish it from spotify_profile and spotify_artist_playlists without opening a schema.

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?

Explicitly routes the agent to three alternatives (spotify_profile for profile details, spotify_artist_playlists for artist playlists, spotify_playlists_search for playlist search), which gives clear selection context. It stops short of stating when-not to use it or naming the exact condition that selects each sibling, so it is strong but not fully explicit.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?