Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

spotify_home

Read-only

Returns normalized shelves and items from Spotify's Web Player home Pathfinder response. The endpoint fetches anonymous Spotify credentials at request time; caller-supplied Spotify bearer or client tokens are not required. sectionItemsLimit: Per-section item limit, clamped to 1-50, default 10. timeZone: IANA time zone for home personalization, e.g. UTC, default UTC. Use spotify_section to retrieve Spotify browse section.

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

Input Schema

NameRequiredDescriptionDefault
spTNoSpotify session token (sp_t) value; a random UUID is generated when omitted.
facetNoSpotify home facet filter, e.g. music, podcasts, audiobooks.
timeZoneNoIANA time zone for home personalization, e.g. UTC, default UTC.
sectionItemsLimitNoPer-section item limit, clamped to 1-50, default 10.
includeEpisodeContentRatingsV2NoInclude Spotify episode content ratings v2 when true.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely useful behavioral context that authentication is handled anonymously at request time and caller bearer/client tokens are not required. It still omits pagination and response-shape behavior, but the auth disclosure is real added value.

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 core return statement, then auth, then the two most important parameter notes and an alternative tool. A couple of param sentences duplicate schema text verbatim, which is minor waste but not harmful.

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?

With an output schema present, the description need not explain return values, and it covers purpose, auth behavior, and key parameter defaults. The one gap is the unresolved overlap with spotify_podcasts_home, but otherwise an agent has enough to call it correctly.

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%, so the schema already documents all five parameters. The description merely restates sectionItemsLimit and timeZone verbatim without adding format, interaction, or defaulting nuance, and says nothing extra about spT, facet, or includeEpisodeContentRatingsV2.

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?

'Returns normalized shelves and items from Spotify's Web Player home Pathfinder response' states a clear verb (returns) and resource (home shelves/items) with normalization scope. It does not distinguish itself from the sibling spotify_podcasts_home, which is a different home surface, so an agent could confuse the two.

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?

It names spotify_section as the alternative for retrieving Spotify browse sections, which gives one routing signal. However, it never states the positive case for using this tool (e.g. 'use for the general Web Player home feed') nor distinguishes from spotify_podcasts_home, so guidance is implied rather than explicit.

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

All Crawlora MCP toolsInspect
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