Crawlora MCP

spotify_playlist

Read-only

Returns normalized Spotify Web Player playlist metadata and items from Spotify's fetchPlaylist Pathfinder response. Provide either uri or id; defaults to a known public playlist when omitted. limit: Playlist item limit, clamped to 1-50, default 25. offset: Playlist item offset, default 0. Use spotify_playlists_search to search Spotify playlists.

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

Input Schema

Name	Required	Description
`id`	No	Spotify playlist ID, used when uri is omitted.
`uri`	No	Spotify playlist URI or open.spotify.com playlist URL.
`limit`	No	Playlist item limit, clamped to 1-50, default 25.
`offset`	No	Playlist item offset, default 0.
`enableWatchFeedEntrypoint`	No	Enable the Spotify watch-feed entrypoint when true.
`includeEpisodeContentRatingsV2`	No	Include Spotify episode content ratings v2 when true.

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 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context: the data is normalized from Spotify's fetchPlaylist Pathfinder response, it defaults to a known public playlist when id/uri are omitted, and limit is clamped to 1-50. These are useful traits beyond the annotations, though return shape and pagination semantics aren't discussed (and an output schema exists).

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?

Purpose is front-loaded and the alternative tool is placed last, which reads well. However, the limit/offset sentences duplicate schema text, which is minor waste in an otherwise tight definition.

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 described, and annotations cover the safety profile. The description covers input selection and the no-argument default, making it largely complete; the two obscure boolean flags are left entirely to the schema.

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 coverage is 100%, so baseline is 3. The description restates the limit and offset semantics verbatim from the schema and only adds the id/uri either-or rule, which the schema already documents ('used when uri is omitted'). Marginal added value over the structured fields.

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 ('Returns') and resource ('playlist metadata and items'), and names the sibling spotify_playlists_search as the alternative for searching. An agent can distinguish this retrieval tool from search-oriented siblings 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: 'Provide either uri or id' and 'Use spotify_playlists_search to search Spotify playlists', plus the fallback behavior when neither is supplied. It lacks explicit guidance versus other playlist-adjacent siblings (e.g. spotify_profile_playlists, spotify_artist_playlists), so it stops short of a full 5.

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.