Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_artist

Retrieve Spotify artist details by ID, URI, or URL, including follower count, monthly listeners, top tracks, discography, and related artists.

Instructions

Retrieve Spotify artist details. Returns a Spotify artist's profile by artist URI, open.spotify.com URL or id: name, verified flag, follower count, monthly listeners (monthlyUsers), biography and images, plus top tracks, selected discography, related artists and artist playlists when Spotify returns them.

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

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the conditional nature of some sections ('when Spotify returns them'). However, it omits auth requirements, rate limits, and — importantly — the odd fact that both id and uri are optional, leaving unclear whether either alone is sufficient or one is preferred.

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, front-loaded with the purpose followed by the return payload. The field list is long but every item is informative; nothing is 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 read-only lookup with no output schema, the description compensates by enumerating the returned fields (name, verified flag, followers, monthlyUsers, bio, images, top tracks, discography, related, playlists). The remaining gap is not clarifying how the two optional identifiers combine.

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 baseline is 3. The description restates that an artist can be given by URI, open.spotify.com URL or id, marginally reinforcing the schema's own param descriptions but adding no format or precedence detail beyond them.

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 and resource ('Retrieve Spotify artist details') and enumerates the profile fields returned. An agent can identify it as the single-artist lookup, though the description does not distinguish it from overlapping siblings like spotify_artist_albums, spotify_artist_related and spotify_artist_playlists, which it partially duplicates with 'top tracks, selected discography, related artists and artist playlists'.

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 when-to-use guidance is given. It never says to first resolve an artist via spotify_artists_search, nor when to prefer the dedicated discography/related/playlist siblings. The only contextual note, 'when Spotify returns them,' describes variability in the response, not usage.

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