Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_genre

Fetch Spotify page data by genre or URI, returning normalized sections and items from the browsePage Pathfinder response with pagination controls for sections and pages.

Instructions

Retrieve Spotify genre page. Returns normalized sections and items from Spotify's browsePage Pathfinder response for a Spotify genre or page URI.

Input Schema

TableJSON 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

B3.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions retrieval and return of sections/items, but does not explain pagination behavior (despite having pagination parameters), side effects, or required permissions. The technical 'browsePage Pathfinder response' is not elaborated.

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?

Two sentences: first states core purpose, second adds technical context. No wasted words, but could be structured more clearly (e.g., list parameters or behavior).

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

Completeness2/5

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

With 6 parameters, no output schema, and no annotations, the description is insufficient. It does not explain the distinction between page and section pagination, return format, or how parameters interact. Agents may struggle to invoke 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 coverage is 100%, so each parameter has a description in the schema. The description adds no additional meaning beyond what is already in the schema, achieving baseline.

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?

Clearly states action ('Retrieve') and resource ('Spotify genre page'), and mentions the return type ('normalized sections and items'). However, does not explicitly differentiate from sibling tools like spotify_section or spotify_home, which may also deal with sections.

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?

Implied usage from description (for genre or page URIs), but no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions.

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