Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_featured_charts_by_country

Fetch Spotify country charts and hub content, such as popular albums, artists, and trending songs, by two-letter country code.

Instructions

Retrieve Spotify featured charts by country. Returns Spotify country hub content. Defaults to the CHARTS content shelf for the requested country.

Input Schema

NameRequiredDescriptionDefault
content_idNoCountry hub content ID. Allowed: CHARTS, POPULAR_ALBUMS, POPULAR_ARTISTS, TRENDING_SONGS
country_codeNoTwo-letter Spotify popular-in country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / content_id / enum
      Added value: +[
+  "CHARTS",
+  "POPULAR_ALBUMS",
+  "POPULAR_ARTISTS",
+  "TRENDING_SONGS"
+]
  2. First observedv1.0.0

TDQS

B3.3/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 usefully discloses that content_id defaults to the CHARTS shelf (a behavior the schema's empty required list does not state), but says nothing about what happens when country_code is omitted, whether results are ranked, or auth/pagination behavior.

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 short, front-loaded sentences with no filler. The core action is stated first and the default-value nuance follows, so nothing needs to be hunted for.

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?

For a simple two-parameter read tool with no output schema, the description is adequate but thin. With zero annotations it could reasonably say more about the shape of the returned hub content and the country-code default, so it is only minimally 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 coverage is 100%, so both parameters are fully documented in the schema, making 3 the baseline. The description adds one genuine detail the schema lacks (the CHARTS default), but otherwise adds no format or meaning beyond the enum and country-code text.

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 featured charts by country') and clarifies it returns country hub content. It's clear what the tool does, but it never contrasts itself with the very close sibling spotify_popular_by_country, so the agent must infer the difference.

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 when-to-use or when-not-to-use guidance and no named alternatives. The only routing hint is the implicit default to the CHARTS shelf, which does not tell the agent how this differs from spotify_popular_by_country or spotify_home.

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