Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_search

Search the Spotify catalog across tracks, artists, albums, playlists, shows, episodes, audiobooks, and top results; no caller-supplied tokens required.

Instructions

Search Spotify catalog. Returns Spotify catalog search results across tracks, artists, albums, playlists, shows, episodes, audiobooks, and top results. Caller-supplied Spotify bearer or client tokens are not required.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term
limitNoResult limit per section, clamped to 1-50
offsetNoSearch offset
is_prefixNoTreat the search term as a prefix
include_authorsNoInclude authors
include_audiobooksNoInclude audiobook results
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_artist_has_concerts_fieldNoInclude artist concert availability fields
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

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 are provided, so the description carries the full behavioral burden. It usefully discloses that caller-supplied Spotify bearer/client tokens are not required (an auth detail an agent needs), but says nothing about pagination, result ordering, or how the many boolean include_* flags affect 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.

Conciseness5/5

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

Three tight sentences with the core purpose front-loaded and no filler. Every sentence conveys distinct information: purpose, coverage, and auth.

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 an 11-parameter tool with no output schema and no annotations, the description is only minimally sufficient. It covers what is searched and the auth model, but omits how the category-specific sibling tools relate and how the boolean flags shape results, which matters for correct invocation.

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 11 parameters are already documented in the schema, giving a baseline of 3. The description adds no syntax, format, or interaction detail beyond what the schema fields provide.

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 clear verb+resource ('Search Spotify catalog') and enumerates the result categories it covers, which conveys a unified cross-category search. However, it never distinguishes itself from the numerous sibling search tools (spotify_tracks_search, spotify_albums_search, spotify_artists_search, etc.), leaving the agent to infer the routing.

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?

There is no when-to-use or when-not-to-use guidance. With roughly eight sibling category-specific search tools present, an agent has no signal for choosing this general search over, say, spotify_albums_search. The description implies broad usage but states no conditions.

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