Crawlora MCP

spotify_popular_by_country

Read-only

Fetch normalized Spotify popular-in country-hub shelf items by countryCode, using codes from public /popular-in/{country} pages. Use spotify_featured_charts_by_country for chart lists or spotify_home for the general home surface.

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_popular_by_country"
  }
}

Input Schema

Name	Required	Description	Default
`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 7, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description still adds genuine context beyond them: that items are 'normalized', that they are shelf items within a country hub, and that codes derive from public /popular-in/{country} pages (provenance). It does not mention pagination or rate limits, so not a 5.

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?

Two compact sentences, purpose front-loaded, sibling routing second. Every clause earns its place with no redundant restatement of the schema.

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

Completeness5/5

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

An output schema exists so return values needn't be described, and annotations cover the safety profile. Combined with clear purpose, code provenance, and sibling routing, the description gives an agent everything needed to select and invoke the tool correctly.

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% and the parameter already documents the two-letter code with examples and a default, so the schema carries most of the load. The description adds marginal meaning by tying valid codes to the public /popular-in/{country} pages, clarifying the code domain beyond the schema.

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?

States a specific verb (Fetch) and resource (normalized Spotify popular-in country-hub shelf items) and names the sibling tools it is NOT, so an agent can distinguish it from spotify_featured_charts_by_country and spotify_home without opening schemas.

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

Usage Guidelines5/5

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

Explicitly routes the agent to alternatives with conditions: spotify_featured_charts_by_country 'for chart lists' and spotify_home 'for the general home surface'. This is a clear when-not signal plus an implied when-to (wanting the popular-in shelf), leaving little to inference.

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.