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-specific featured charts and content shelves like popular albums, artists, or trending songs using a two-letter country code.

Instructions

Retrieve Spotify featured charts by country. Returns normalized Spotify country hub content from Spotify's countryHubContent Pathfinder response. Defaults to the CHARTS content shelf for the requested country.

Input Schema

TableJSON 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

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the default shelf but does not disclose pagination, error handling, rate limits, or whether the operation is read-only. The return content is described vaguely as 'normalized content' without specifying structure or possible failures.

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?

The description is concise and front-loaded with the primary action. It uses three short sentences without fluff, but could be slightly more structured to separate the purpose, default behavior, and source. Overall it is efficient.

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

Completeness2/5

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

Given the lack of an output schema and annotations, the description should explain what the agent will receive. It only says 'normalized content' without describing the shape, fields, or whether it is a list. It also does not mention any prerequisites or limitations (e.g., supported countries). This is insufficient for an agent to confidently call the tool.

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% with descriptions for both parameters, so the baseline is 3. The description adds the default value for content_id (CHARTS), which is useful context beyond the schema. However, it does not elaborate on the country_code format or how it relates to the response, so the added value is marginal.

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?

The description clearly states the tool retrieves Spotify featured charts by country and mentions the specific data source (countryHubContent Pathfinder response). It also notes the default CHARTS content shelf. This is a specific verb+resource, though it does not explicitly differentiate from similar siblings like spotify_popular_by_country.

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 is provided on when to use this tool versus alternatives. There is no mention of alternative tools, conditions, or exclusions. The description only states the default behavior, not usage context.

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