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 structured track results without requiring Spotify bearer or client tokens.

Instructions

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

Input 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.2/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It usefully states that caller-supplied bearer or client tokens are not required, but it does not describe pagination, result limits, rate limits, or other search behavior beyond returning results.

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?

The description is short and front-loaded with the core action. The second sentence restates the search behavior somewhat redundantly, but the structure remains efficient and readable.

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 search tool with nine fully-documented parameters and no output schema, the description covers purpose and authentication but omits result shape, pagination, and differentiation from other Spotify search tools. It is adequate but 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?

Schema description coverage is 100%, so the schema already documents all nine parameters. The description adds no parameter-specific meaning beyond the basic search term, making the baseline 3 appropriate.

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?

The description uses a specific verb and resource: 'Search Spotify tracks' and returning track search results. It is clear what the tool does, but it does not distinguish it from nearby siblings such as spotify_search or spotify_track, so an agent must infer routing from the name alone.

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?

It implies use for track searches but gives no explicit when-to-use guidance, exclusions, or alternatives. With many spotify siblings available, the lack of routing guidance is a meaningful gap.

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