spotify_tracks_search
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.
This record as markdown: /tools/crawlora-mcp/spotify-tracks-search.md
What spotify_tracks_search does on Crawlora
AI agents call spotify_tracks_search to retrieve information from Crawlora without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | Search term |
limit | integer | — | Track result limit, clamped to 1-50 |
offset | integer | — | Search offset |
include_authors | boolean | — | Include authors |
include_audiobooks | boolean | — | Include audiobook context where available |
include_pre_releases | boolean | — | Include pre-release results |
number_of_top_results | integer | — | Top result limit, clamped to 1-50 |
include_album_pre_releases | boolean | — | Include album pre-release results |
include_episode_content_ratings_v2 | boolean | — | Include Spotify episode content ratings v2 |
Parameters from the server's own tool schema.
Why spotify_tracks_search is rated Low
Even though spotify_tracks_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs spotify_tracks_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crawlora, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_tracks_search, this is the rule to start with:
spotify_tracks_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crawlora, apply this rule, and every spotify_tracks_search call is checked against it from then on.
Questions about spotify_tracks_search
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. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
spotify_tracks_search accepts 9 parameters: q, limit, offset, include_authors, include_audiobooks, include_pre_releases, number_of_top_results, include_album_pre_releases, include_episode_content_ratings_v2. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for spotify_tracks_search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Crawlora. Nothing to install.
spotify_tracks_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spotify_tracks_search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for spotify_tracks_search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
spotify_tracks_search is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue