Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_track_recommended

Retrieve Spotify track recommendations from a track URI, URL, or ID. Returns recommended tracks with metadata and images, limited to 1-50 results.

Instructions

Retrieve Spotify recommended tracks. Returns Spotify's recommendations for a track, given its URI, open.spotify.com URL or track id. Each recommendation has a type, title, subtitle, description, Spotify URI, external URL and images. limit is clamped to 1-50 and defaults to 5.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify track ID. Used when uri is omitted
uriNoSpotify track URI or open.spotify.com track URL
limitNoRecommendation limit, clamped to 1-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the return shape (type, title, subtitle, description, URI, external URL, images) and the limit clamping/default, but says nothing about authentication requirements, rate limits, or whether an id-less call behaves differently. Partial disclosure only.

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 sentences, front-loaded with the purpose, then input forms, then return shape and the limit rule. The return-field enumeration is somewhat listy but earns its place since no output schema exists. No filler.

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?

With no annotations and no output schema, the description sensibly covers return fields and the limit rule. However it omits auth expectations, error/failure behavior for invalid ids, and any pagination or endpoint-scope notes, leaving gaps for a 3-parameter read tool.

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 explains id, uri, and limit. The description adds the default value of 5 (not in the schema) and restates the accepted URI/URL forms, but does not clarify the id-vs-uri precedence beyond what the schema's 'Used when uri is omitted' already provides. Baseline 3 with a small increment for the default.

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+resource ('Retrieve Spotify recommended tracks') and clarifies the input is a track URI, open.spotify.com URL, or track id, which separates it from track search tools. It does not explicitly name or differentiate from the closest recommendation siblings (e.g. spotify_track_similar_albums, spotify_artist_related), so it falls 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: give a known track id/URI to get Spotify's recommendations. There is no explicit when-to-use guidance, no statement of when this beats spotify_track_similar_albums or spotify_artist_related, and no 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