Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apple_podcasts_show

Fetch Apple Podcasts show details by Apple show ID, including name, artist, feed URL, genre, episode count, release date, rating, and artwork. Set country and language for storefront.

Instructions

Retrieve Apple Podcasts show details. Returns the details of one Apple Podcasts show by its Apple show id: collection_name, artist_name, feed_url, primary_genre_name, genres, track_count, release_date, content advisory rating and artwork. country and lang choose the storefront and language.

Input Schema

NameRequiredDescriptionDefault
idYesApple Podcasts show ID
langNoResult language tag
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 burden; it discloses this is a per-id retrieval and enumerates the returned fields (collection_name, feed_url, track_count, artwork, etc.), which is genuinely useful since there is no output schema. However it says nothing about error behavior for unknown ids, rate limits, or the fact that results are scoped by storefront — the read-only nature is only implied by 'Retrieve'.

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?

Two tight sentences, purpose front-loaded, no filler. The long field enumeration is justified given no output schema documents the return shape.

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 simple read-by-id tool with full schema coverage, the definition is largely complete: it states the key, the storefront/language controls, and the returned fields in lieu of an output schema. It only lacks error/edge-case behavior and routing to the search sibling for id discovery.

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 all three params are already documented. The description adds only that country/lang 'choose the storefront and language,' which is largely redundant with the schema's 'Two-letter storefront country code' and 'Result language tag'. Baseline 3 is 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?

States a specific verb (Retrieve) and resource (Apple Podcasts show details) resolved by an Apple show `id`, which clearly separates it from the sibling feed/list tools like apple_podcasts_search or apple_podcasts_charts. It stops short of naming any sibling explicitly, so an agent must infer that this is the by-id detail endpoint.

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 guidance on when to use this tool versus apple_podcasts_search or apple_podcasts_show_episodes, and no note that you must first obtain an id from a search tool. Usage is only implied by 'by its Apple show id'.

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