Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_profile

Retrieve public Spotify profile metadata and preview playlists by providing username, URI, or URL. Defaults to Spotify's official profile.

Instructions

Retrieve Spotify public profile. Returns public Spotify profile metadata and preview playlists. Provide username, uri, or url; defaults to Spotify's official profile.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify user URI
urlNoopen.spotify.com user URL
usernameNoSpotify username
artist_limitNoRecently played artist limit, clamped to 0-50
episode_limitNoEmbedded episode limit, clamped to 0-50
playlist_limitNoEmbedded public playlist limit, clamped to 0-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It conveys that the data is 'public' (implying no privileged auth) and that it returns metadata plus preview playlists, but omits rate limits, pagination, or what specific fields come back. Adequate but thin for a no-annotation tool.

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 compact sentences, front-loaded with the core action and followed by return content and input guidance. No wasted filler, though the 'preview playlists' detail slightly muddies the boundary with spotify_profile_playlists.

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?

With no output schema, the description helpfully names what is returned (metadata and preview playlists) and how to identify the target profile. For a read-only profile tool this is largely complete, though behavior under missing/invalid identifiers is unstated.

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 six parameters are already fully documented in the schema. The description restates the three identifier options (username/uri/url) but adds no syntax or constraint detail beyond the schema; the three limit params are not mentioned at all. Baseline 3 is appropriate.

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 ('Retrieve') and resource ('Spotify public profile') and describes the return payload (profile metadata and preview playlists). It does not explicitly differentiate itself from close siblings like spotify_profile_playlists or spotify_profiles_search, so an agent may hesitate among them.

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?

Gives input guidance ('Provide username, uri, or url; defaults to Spotify's official profile'), which is useful context for invocation. However, there is no explicit when-to-use guidance, no when-not-to-use, and no named alternatives among the many spotify_profile_* siblings.

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