Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_genre

Fetch Spotify genre or browse page sections with pagination limits and offsets, returning titles, item details, images, and URLs for each section.

Instructions

Retrieve Spotify genre page. Returns the sections of a Spotify genre or browse page for uri (default spotify:page:0JQ5DAB3zgCauRwnvdEQjJ). Each section has a title, type, totalCount and items with title, subtitle, image and Spotify URL. page_limit and section_limit default to 10 and run 1 to 50; matching offsets default to 0.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify genre or page URI
page_limitNoPage pagination limit, clamped to 1-50
page_offsetNoPage pagination offset
section_limitNoSection pagination limit, clamped to 1-50
section_offsetNoSection pagination offset
include_episode_content_ratings_v2NoInclude Spotify episode content ratings v2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (sections with title, type, totalCount, and items with title/subtitle/image/URL) and the pagination defaults. It omits any auth or rate-limit context, keeping it from 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?

Front-loaded with purpose, then return format, then pagination semantics. Every sentence adds information and there is no filler.

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 no output schema and no annotations, the description compensates by describing the returned sections and items in detail and covering defaults. It is complete enough to call correctly, though a note on how it relates to sibling browse tools would make it fully self-contained.

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%, so the baseline is 3, but the description adds value by stating the default values (page_limit/section_limit default to 10, offsets default to 0) beyond the schema's clamping note. This meaningfully clarifies parameter behavior.

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 (Retrieve) and resource (Spotify genre/browse page), and clarifies the tool accepts either a genre or browse page URI. It does not explicitly differentiate itself from closely related siblings like spotify_section or spotify_home, so it stops short of a 5.

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?

Usage is implied: you call it to fetch a genre page, and a sensible default URI is provided when none is given. However, there is no explicit when-to-use versus alternatives such as spotify_section, and no exclusions or prerequisites are stated.

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