Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_artist_related

Retrieve artists related to a given Spotify artist using an ID, URI, or open.spotify.com URL, returning titles, URIs, external links, and images for music discovery.

Instructions

Retrieve Spotify related artists. Returns the artists Spotify lists as related to a given artist, by artist URI, open.spotify.com URL or id. Each related artist has a title, Spotify URI, external URL and images. An invalid identifier returns 400.

Input Schema

NameRequiredDescriptionDefault
idNoSpotify artist ID
uriNoSpotify artist URI or open.spotify.com artist URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape (title, Spotify URI, external URL, images) and error behavior (invalid identifier returns 400), which is concrete and useful. It omits auth requirements and rate limits, keeping it short of 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?

Three tight sentences, front-loaded with purpose, then accepted input forms, then return contents and error behavior. Zero 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?

For a simple read tool with no output schema and no annotations, the description covers purpose, accepted inputs, return fields, and the failure case, so an agent has what it needs to call it. It stops short of mentioning rate limits or whether the list is paginated.

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 documents both parameters. The description adds only marginal mapping value by noting identifiers may be a URI, open.spotify.com URL, or id, which largely restates the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 related artists) that is clearly distinct from siblings like spotify_artist and spotify_artist_albums. An agent can tell it apart without opening any schema.

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 only implied: it tells you an artist URI, open.spotify.com URL, or id is required as input, but gives no when-to-use guidance, no prerequisites, and never names an alternative (e.g. spotify_artists_search to find an artist id first). Adequate but with clear gaps.

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