Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_tracks_search

Search Spotify tracks by keyword and return normalized Web Player results, using anonymous credentials so no Spotify token is required.

Instructions

Search Spotify tracks. Returns normalized Spotify Web Player track search results for a search term. The endpoint fetches anonymous Spotify credentials at request time; caller-supplied Spotify bearer or client tokens are not required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch term
limitNoTrack 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

B3.4/5.0
Behavior3/5

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

The description reveals that the tool fetches anonymous credentials at request time, indicating no auth needed. However, it does not disclose rate limits, error handling, or response structure beyond 'normalized results'. With no annotations, more behavioral context would be beneficial.

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?

Two sentences conveying key information: purpose and a notable behavior (no auth). No wasted words, but could be more structured. Adequately concise.

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 tool with 9 parameters and no output schema, the description covers the core purpose and one behavioral trait. However, it lacks explanations of how parameters interact (e.g., offset vs top_results) and does not describe return format. Moderately incomplete.

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?

All 9 parameters have schema descriptions, so the description adds no extra parameter meaning. The description's mention of 'search term' merely repeats the schema. Baseline score of 3 is appropriate as schema coverage is 100%.

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?

Clearly states 'Search Spotify tracks' with specific verb and resource. The description mentions normalized results and anonymous credentials, which adds clarity. However, it does not explicitly differentiate from sibling tools like spotify_search or spotify_albums_search, leaving room for confusion.

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?

Mentions that caller-supplied tokens are not required, which is helpful context. But it lacks guidance on when to use this tool versus alternatives (e.g., spotify_search for broader search). No exclusion criteria or prerequisites are provided.

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