Crawlora MCP

spotify_featured_charts_by_country

Read-only

Returns normalized Spotify country hub content from Spotify's countryHubContent Pathfinder response. Defaults to the CHARTS content shelf for the requested country. contentId: Country hub content ID. Allowed values: CHARTS, POPULAR_ALBUMS, POPULAR_ARTISTS, TRENDING_SONGS. Default CHARTS. countryCode: Two-letter Spotify popular-in country code, e.g. US, default us. Use spotify_popular_by_country to retrieve Spotify popular by country.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_featured_charts_by_country"
  }
}

Input Schema

Name	Required	Description	Default
`contentId`	No	Country hub content ID. Allowed values: CHARTS, POPULAR_ALBUMS, POPULAR_ARTISTS, TRENDING_SONGS. Default CHARTS.
`countryCode`	No	Two-letter Spotify popular-in country code, e.g. US, default us.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and network scope are covered. The description adds that it returns normalized data from Spotify's countryHubContent Pathfinder response and that it defaults to the CHARTS shelf, which is useful but modest context; no pagination or completeness notes.

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?

Front-loaded with the return behavior and default before parameter recap, with only one jargon-heavy clause ('countryHubContent Pathfinder response') that partially earns its place by identifying the data source. Slightly redundant with the schema's parameter descriptions.

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?

An output schema exists, annotations cover the safety profile, and both parameters are documented at 100% coverage, so the description does not need to explain return values. It is complete enough for correct invocation; only richer when-to-use detail is missing.

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 description coverage is 100%, and the description reproduces the same contentId/countryCode wording as the schema verbatim, adding no format or syntax detail beyond it. Baseline 3 is appropriate when the schema carries the parameter burden.

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 clear verb+resource (returns Spotify country hub content / featured charts by country) and names the sibling spotify_popular_by_country as a distinct capability. The mention of the countryHubContent Pathfinder source adds specificity, though the phrase 'normalized ... content' is a bit vague about the actual payload.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly points the agent to the alternative: 'Use spotify_popular_by_country to retrieve Spotify popular by country,' which implicitly frames this tool as the charts/content-shelf route rather than the popular route. It does not state the positive condition for choosing this tool, so no full when/when-not pair.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?