Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_profile

Fetch a Spotify user's public profile metadata and preview playlists by username, URI, or URL; defaults to Spotify's official profile.

Instructions

Retrieve Spotify public profile. Returns normalized public profile metadata and preview playlists from Spotify's Web Player user-profile service. Provide username, uri, or url; defaults to Spotify's official profile.

Input Schema

TableJSON 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

B3.4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses the source service (Spotify's Web Player user-profile service) and default behavior. However, it does not mention authentication needs, rate limits, or side effects. Since it's a retrieval, it is likely read-only but not explicitly stated.

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?

Two concise sentences. First sentence states purpose, second sentence gives input guidance and default. No fluff or redundant information.

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?

Explains what is returned (metadata and preview playlists) and the source, but lacks detail on output structure or edge cases (e.g., invalid username). Without output schema, more description of the return format would be helpful. Adequate but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds value by grouping username, uri, url as alternative identifiers and stating the default behavior (official profile). The integer limits are well-described in the schema, so no additional detail needed.

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?

Clearly states the action (Retrieve) and resource (Spotify public profile) and mentions it returns 'normalized public profile metadata and preview playlists'. However, it does not explicitly distinguish from sibling tools like spotify_profile_followers or spotify_profile_playlists, which are more specific.

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?

Provides input guidance (provide username, uri, or url; defaults to official profile) but does not explain when to use this tool over alternatives like spotify_profile_followers or spotify_profile_playlists. No explicit when-to-use or when-not-to-use advice.

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