Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_podcasts_charts

Retrieve Spotify podcast chart rankings by chart type and region, including top podcasts, episodes, trending, and supported category charts.

Instructions

Retrieve Spotify podcast charts. Returns 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

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.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 full burden. It does disclose meaningful behavior: parameter values are validated against supported slugs/countries and category charts are region-restricted. It does not mention authentication, caching, or pagination, and there is no output schema to cover the return shape.

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 sentences, front-loaded with the core action, with no filler. Minor redundancy between 'Retrieve Spotify podcast charts' and 'Returns Spotify podcast chart rankings from...' costs it a point.

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 three-parameter retrieval tool with no annotations and no output schema, the description covers the input side well, including the important cross-parameter constraint. A brief indication of what a ranking entry contains would close the remaining gap, since no output schema exists to carry it.

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% with both enums fully enumerated, so the baseline is met by the schema alone. The description adds genuine meaning beyond it by explaining that chart and region are validated against supported slugs/countries and by documenting the chart-type/region interaction (category charts limited to seven countries).

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 ('Retrieve Spotify podcast charts') and names the upstream source (podcastcharts.byspotify.com). However, it does not differentiate itself from close siblings such as spotify_featured_charts_by_country, spotify_podcasts_categories, or apple_podcasts_charts, so an agent must infer the distinction.

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?

There is a usable conditional hint ('Category charts are available only in au, br, de, gb, mx, se, and us'), which tells the agent when a category chart request will succeed. But there is no explicit when-to-use guidance or routing to the many sibling chart/podcast tools, so usage is only implied.

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