Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_track_recommended

Fetch recommended Spotify tracks for a given track ID or URI, with an optional limit, and return normalized recommendation data.

Instructions

Retrieve Spotify recommended tracks. Returns normalized recommended Spotify entities from the internalLinkRecommenderTrack Pathfinder response.

Input Schema

TableJSON 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

C2.9/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It mentions a source ('internalLinkRecommenderTrack Pathfinder') but fails to describe safety (e.g., read-only?), authentication, rate limits, or whether it mutates state. This is insufficient for transparent decision-making.

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?

The description is two sentences, front-loading the core purpose. The second sentence adds technical detail about the data source. While every sentence earns its place, the second could be clearer about output format. Overall efficient.

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?

The tool has no output schema and 3 parameters with no required fields. The description says 'returns normalized recommended Spotify entities' but does not specify what fields those entities contain, nor that at least one of 'uri' or 'id' is needed. For a recommendation tool, more detail on return format is expected.

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?

All three parameters have descriptions in the JSON schema (100% coverage). The tool description does not add new parameter-specific context. The baseline of 3 applies since the schema already documents each parameter, though the description could clarify the relationship between 'uri' and 'id' (e.g., that one is expected).

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?

The description clearly states 'Retrieve Spotify recommended tracks', which is a specific verb+resource. While it doesn't explicitly differentiate among the many Spotify tools, the name and focus on recommendations make its purpose distinct from siblings like spotify_track or spotify_album.

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 guidelines are provided on when to use this tool versus alternatives (e.g., spotify_track_similar_albums or spotify_artist_related). There is no mention of prerequisites, context, or exclusion criteria, leaving the AI agent without guidance on tool selection.

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