Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

spotify_genre

Read-only

Fetch normalized sections and content items for a Spotify genre or browse-page URI. Use spotify_section for other browse-page sections, spotify_home for the homepage, or spotify_podcasts_categories for podcast categories.

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

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify genre or page URI, e.g. spotify:genre:podcasts-web.
pageLimitNoPage pagination limit, clamped to 1-50, default 10.
pageOffsetNoPage pagination offset, default 0.
sectionLimitNoSection pagination limit, clamped to 1-50, default 10.
sectionOffsetNoSection pagination offset, default 0.
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

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing about pagination behavior across the two paginated layers (page* vs section*), rate limiting, or what 'normalized' means—useful behavioral context that is missing. Baseline 3 with annotations carrying the safety load.

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 sentences, front-loaded with the core action and immediately followed by the disambiguation routing. 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?

An output schema exists, so return values need not be explained, and the schema fully documents parameters. The main gap is the interaction between pageLimit/pageOffset and sectionLimit/sectionOffset—a two-level pagination model the description doesn't clarify, which matters for a browse tool with six optional params.

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 all six parameters are documented in the schema (including clamping ranges and defaults). The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 ('Fetch') and resource ('normalized sections and content items for a Spotify genre or browse-page URI'), which is concrete. It doesn't explicitly contrast with spotify_home/spotify_section except via the routing sentence, and the term 'normalized' is left unexplained, 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 Guidelines5/5

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

Explicitly names three sibling alternatives (spotify_section, spotify_home, spotify_podcasts_categories) and the conditions that select each, routing the agent precisely. This is exactly the when-to-use-this-vs-alternatives guidance the dimension rewards.

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