Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_charts

Fetch Spotify podcast chart rankings by region and chart type, with normalized results for top podcasts, episodes, trending, and supported categories.

Instructions

Retrieve Spotify podcast charts. Returns normalized Spotify podcast chart rankings from podcastcharts.byspotify.com. The chart and region parameters are validated against Spotify's supported podcast chart slugs and countries. Category charts are available only in au, br, de, gb, mx, se, and us.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chartNoChart slug. Allowed: top-podcasts, top-episodes, trending, arts, business, comedy, education, fiction, health-fitness, history, leisure, music, news, religion-spirituality, science, society-culture, sports, technology, true-crime, tv-film
limitNoResult limit, clamped to 1-100
regionNoTwo-letter region code. Allowed: ar, au, at, br, ca, cl, co, dk, fi, fr, de, in, id, ie, it, jp, mx, nz, no, ph, pl, es, se, nl, gb, us

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / chart / enum
      Added value: +[
+  "top-podcasts",
+  "top-episodes",
+  "trending",
+  "arts",
+  "business",
+  "comedy",
+  "education",
+  "fiction",
+  "health-fitness",
+  "history",
+  "leisure",
+  "music",
+  "news",
+  "religion-spirituality",
+  "science",
+  "society-culture",
+  "sports",
+  "technology",
+  "true-crime",
+  "tv-film"
+]
    • addedInput schema / properties / region / enum
      Added value: +[
+  "ar",
+  "au",
+  "at",
+  "br",
+  "ca",
+  "cl",
+  "co",
+  "dk",
+  "fi",
+  "fr",
+  "de",
+  "in",
+  "id",
+  "ie",
+  "it",
+  "jp",
+  "mx",
+  "nz",
+  "no",
+  "ph",
+  "pl",
+  "es",
+  "se",
+  "nl",
+  "gb",
+  "us"
+]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the source, that rankings are normalized, that chart and region are validated, and the country restriction for category charts. However, it does not explain default behavior when optional parameters are omitted (all params optional) or the returned data shape, leaving gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with no fluff, leading with the core action and then layering source, validation, and a regional caveat. Efficiently front-loads the main purpose.

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

Completeness3/5

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

Adequate for a simple read-only chart retrieval tool, given all parameters are documented in the schema. Still, the absence of an output schema means the description should clarify what the returned rankings look like (e.g., show names, ranks, positions) and what happens when no chart/region is supplied; these are left implicit.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the enum lists by stating that chart and region are validated against Spotify's supported slugs/countries and that category charts are restricted to a specific country set, which helps agents anticipate invalid combinations.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description opens with a specific verb and resource – 'Retrieve Spotify podcast charts' – and adds the data source and normalization behavior. This clearly distinguishes it from sibling podcast tools (search, show, episode, home) by chart-specific scope.

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?

No guidance on when to choose this tool over sibling podcast tools such as spotify_podcasts_search or spotify_podcasts_home. The description states only the tool's operation and constraints, not use-case selection criteria.

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