Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_podcasts_search

Search Apple Podcasts shows by term, with options to refine by country, language, page, and limit. Returns show details including name, artist, feed URL, genres, and artwork.

Instructions

Search Apple Podcasts shows. Searches Apple Podcasts shows by term, which is required. country, lang, limit and page (1-based) refine the search. Each show has collection_name, artist_name, feed_url, primary_genre_name, genres, track_count, release_date, content advisory rating and several artwork sizes.

Input Schema

NameRequiredDescriptionDefault
langNoResult language tag
pageNoSearch page number (1-based)
termYesSearch term
limitNoNumber of shows per page
countryNoTwo-letter storefront country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. 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, the description carries the full behavioral burden. It discloses the return shape (many show fields) and hints at pagination via the 1-based page param, but says nothing about result caps, rate limits, ordering, or how results are ranked.

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 front-loaded sentences: purpose first, then parameters, then return fields. Efficient and well ordered, though the final field list is long, which is defensible given there is no output schema.

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 read-only search with no output schema, the description supplies the missing return-field context and covers the required parameter plus refinements. It leaves ranking, pagination limits, and default values unstated but is otherwise complete.

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 every parameter is already documented in the schema. The description restates them (term required; country/lang/limit/page refine) with minimal added meaning, so the baseline 3 applies.

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") and the resource scope ("shows", not episodes) implicitly distinguishes it from siblings like apple_podcasts_episodes_search. However, it never explicitly names an alternative or clarifies the boundary versus apple_podcasts_show or apple_podcasts_charts.

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?

The description explains which parameters exist but gives no when-to-use or when-not-to-use guidance. It never says when to prefer this search over episode search, charts, or the show-detail tool, leaving routing 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