Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_apple_podcasts_shows_search

Search Apple Podcasts shows dataset. Searches the crawled public Apple Podcasts show catalog stored in a search index. One row per show.

Instructions

Search Apple Podcasts shows dataset. Searches the crawled public Apple Podcasts show catalog stored in a search index. One row per show. Discovered from a country x genre x collection chart grid and a search-term sweep — not a full catalog of every Apple Podcasts show. Sort enum: relevance, popularity, track_count_desc, release_desc, title_asc. Billing: this search costs 1 credit per record returned, with a minimum of 2 (an empty result costs 2, a full page of 100 costs 100).

Input Schema

NameRequiredDescriptionDefault
qNoFull-text query over show title and artist name, max 256 characters
pageNoPage number, defaults to 1
sortNoSort enum: relevance, popularity, track_count_desc, release_desc, title_asc
genreNoExact primary-genre filter (e.g. Comedy, True Crime), max 128 characters
run_idNoExact crawl run-id filter, max 128 characters
countryNoExact storefront country filter (the crawl's discovery storefront, e.g. us, gb), max 128 characters
genre_idNoExact Apple Podcasts genre id filter (e.g. 1303 for Comedy), max 128 characters
page_sizeNoPage size, defaults to 20 and maxes at 100; page * page_size must be <= 10000
explicitnessNoExact explicitness filter as reported by Apple (e.g. explicit, cleaned), max 128 characters
min_track_countNoMinimum episode count (track_count), 0 or greater

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "popularity",
+  "track_count_desc",
+  "release_desc",
+  "title_asc"
+]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the billing model (1 credit per record, minimum 2, empty result costs 2, full 100-record page costs 100) and the critical coverage caveat that this is NOT a full catalog. Missing pagination/return-format detail, but the cost and coverage disclosures are strong behavioral signals.

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?

Front-loaded with purpose for easy scanning, and the coverage caveat plus billing warning are efficiently packed. The sort enum listing is redundant with the schema, which is the only real waste.

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?

For a 10-parameter, no-output-schema search tool, the description covers the essentials an agent needs: what the dataset is, its coverage limitations, sort options, and cost. Return-value detail is the main gap, but the coverage caveat is the crucial missing piece it does supply.

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 10 parameters. The description only restates the sort enum, which is already fully enumerated in the schema, and adds no meaning beyond it. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb and resource (search Apple Podcasts shows dataset) and clarifies the scope: 'one row per show' from a crawled public catalog. It implicitly distinguishes itself from the sibling _item and _facets tools by being the search entry point, though it never names those siblings explicitly.

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?

It gives important scope context ('discovered from a country x genre x collection chart grid and a search-term sweep — not a full catalog'), which implies when results may be incomplete, but there is no explicit when-to-use guidance or routing to alternatives like datasets_apple_podcasts_shows_item or _facets. Usage is left to inference.

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