Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_playlists_search

Search Spotify playlists by keyword to find public playlist results, no Spotify tokens required. Use it to discover playlists matching any search term.

Instructions

Search Spotify playlists. Returns Spotify playlist search results for a search term. Caller-supplied Spotify bearer or client tokens are not required.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term
limitNoPlaylist result limit, clamped to 1-50
offsetNoSearch offset
include_authorsNoInclude authors
include_audiobooksNoInclude audiobook context where available
include_pre_releasesNoInclude pre-release results
number_of_top_resultsNoTop result limit, clamped to 1-50
include_album_pre_releasesNoInclude album pre-release results
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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 usefully discloses that caller-supplied bearer/client tokens are not required, but says nothing about pagination, rate limits, result ordering, or the shape of the response.

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?

The second sentence ("Returns Spotify playlist search results for a search term") largely restates the first and the third is a distinct behavioral note, so there is some redundancy. Front-loading of the core action is good but a sentence does not fully 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?

For a nine-parameter search tool with no output schema and no annotations, the description is thin on return-value expectations and the purpose of the many include_* toggles, though the schema fully documents each parameter. It is minimally adequate rather than 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 all nine parameters (q, limit, offset, include_* flags) are already documented in the schema. The description adds nothing beyond restating that a search term is consumed, so the baseline 3 applies.

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 ("Search") and resource ("Spotify playlists"), which cleanly separates it from the many sibling search tools like spotify_tracks_search and spotify_albums_search. It does not explicitly name or contrast those siblings, but the resource noun carries the differentiation.

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?

The description offers no when-to-use guidance, no conditions for choosing this over spotify_search or the other typed search endpoints, and no exclusions. Usage is only implied by the word "Search".

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