Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

apple_podcasts_charts

Fetch Apple Podcasts chart rankings for shows or audio podcasts by country, genre, and limit to analyze podcast popularity and discover ranked entries.

Instructions

Retrieve Apple Podcasts chart rankings. Returns Apple Podcasts show chart rankings for a collection, either toppodcasts or topaudiopodcasts. Narrow with category (a numeric Apple podcast genre ID), country and limit. Each entry has name, artist_name, genre, genre_id, description, release_date, artwork_url and url.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of chart items to return
countryNoTwo-letter storefront country code
categoryNoNumeric Apple podcast genre ID
collectionNoChart collection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It conveys a read-only retrieval by naming the return fields, but says nothing about pagination, rate limits, default values for limit/country, or error behavior. Adequate but incomplete for an unannotated tool.

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?

Four compact sentences, front-loaded with the core action and the collection constraint before the narrowing options and return shape. No filler, though the trailing field list is somewhat long without being wasteful.

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?

With no output schema present, the description usefully enumerates the returned entry fields and explains all four parameters, making it usable for an agent. Minor gap: no indication of defaults or how many entries are returned absent a limit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description adds real value beyond the schema by spelling out the two allowed collection values (toppodcasts / topaudiopodcasts) that the schema leaves as an unconstrained string, and by noting category is a numeric genre ID.

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 chart rankings), so the agent knows exactly what the tool produces. However, it does not distinguish itself from the very similar sibling apple_podcasts_charts_rankings, leaving ambiguity when both are present.

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?

Describes how to narrow results with category/country/limit and names the two collection values, which implicitly signals usage. But there is no explicit when-to-use vs. alternatives (e.g. apple_podcasts_search or apple_podcasts_charts_rankings) and no exclusions or prerequisites.

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