Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_home

Retrieve personalized Spotify home sections and shelves. Fetch content items from Spotify home data without requiring session or client tokens.

Instructions

Retrieve Spotify home sections. Returns Spotify home shelves and items. Caller-supplied Spotify bearer or client tokens are not required.

Input Schema

NameRequiredDescriptionDefault
sp_tNoOptional Spotify session token. A random UUID is generated when omitted
facetNoOptional Spotify home facet
time_zoneNoIANA time zone used by Spotify home personalization
section_items_limitNoPer-section item limit, clamped to 1-50
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 burden. It does disclose the notable behavioral fact that caller-supplied bearer/client tokens are not required, which lowers invocation friction, but it says nothing about return format, pagination, rate limits, or personalization behavior beyond a passing mention in the schema.

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?

Three short sentences with the core action front-loaded. There is mild redundancy between 'Retrieve Spotify home sections' and 'Returns Spotify home shelves and items', but nothing wasteful enough to hurt usability.

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 5-parameter read tool with no annotations and no output schema, the description is thin: it never explains what a 'section' or 'facet' yields, whether results are personalized, or how it relates to sibling home/section endpoints. The auth note is the only substantive context added.

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 all five parameters (sp_t, facet, time_zone, section_items_limit, include_episode_content_ratings_v2) are already documented in the schema. The description adds no parameter-level meaning beyond restating that tokens are optional, which is the baseline-3 case when the schema does the heavy lifting.

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 home sections') and clarifies the payload ('home shelves and items'). It does not differentiate from closely named siblings such as spotify_section or spotify_podcasts_home, so an agent cannot tell which home/section tool to pick from the description alone.

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 usage-relevant remark is about authentication, which is not a selection criterion among the many spotify_* siblings.

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