Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_search

Search Spotify podcasts by query and return matching shows, episodes, and top results with counts. Use filters to include pre-releases, audiobooks, or authors.

Instructions

Search Spotify Podcasts. Searches Spotify podcasts for q, returning matching shows, episodes and topResults, with counts in meta. limit and number_of_top_results run 1 to 50. Optional flags (include_pre_releases, include_audiobooks, include_authors) widen the results. Episodes carry duration and release date; shows carry publisher.

Input Schema

NameRequiredDescriptionDefault
qYesPodcast search term
limitNoResult limit, clamped to 1-50
offsetNoSearch offset
include_authorsNoInclude authors
include_audiobooksNoInclude audiobooks
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?

With no annotations provided, the description does carry useful behavioral detail beyond the schema: the response shape (shows/episodes/topResults with counts in meta), the 1-50 clamping on limit and number_of_top_results, and the widening effect of the include_* flags. It still omits any mention of auth requirements, result ordering/relevance, or pagination behavior via offset.

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?

Three tight sentences, front-loaded with the core action and then the return shape. Every sentence carries information with no padding, though the entity/flag listing could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description usefully compensates by describing the returned collections and meta counts, plus what episodes and shows carry. The remaining gap is the lack of any sibling differentiation or offset/pagination note for a 9-parameter search tool.

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 baseline is 3. The description adds marginal color on the flags ('widen the results') and repeats the 1-50 range already in the schema, but it lists only three of the five include_* flags and never explains offset, so it does not meaningfully exceed the schema.

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 Podcasts') and goes further by naming the returned entities (shows, episodes, topResults, meta). However, it never distinguishes itself from near-identical siblings like spotify_episodes_search, spotify_shows_search or spotify_audiobooks_search, which is the one thing an agent most needs to disambiguate among the many Spotify search tools.

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 guidance and no reference to alternatives. With siblings such as spotify_episodes_search and spotify_shows_search in the same family, the agent is left to guess whether this multi-entity search is the right entry point or whether the narrower episode/show search is preferred.

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