Crawlora MCP

spotify_profile

Read-only

Fetch public Spotify profile metadata and preview playlists by username, URI, or URL. Use spotify_profile_followers or spotify_profile_playlists for those dedicated lists, or spotify_profiles_search to find a profile.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spotify_profile"
  }
}

Input Schema

Name	Required	Description
`uri`	No	Spotify user URI, e.g. spotify:user:spotify; provide one of username, uri, or url.
`url`	No	Open Spotify user URL, e.g. https://open.spotify.com/user/spotify; provide one of username, uri, or url.
`username`	No	Spotify username, e.g. spotify; provide one of username, uri, or url.
`artistLimit`	No	Recently played artist limit, clamped to 0-50.
`episodeLimit`	No	Embedded episode limit, clamped to 0-50.
`playlistLimit`	No	Embedded public playlist limit, clamped to 0-50.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-data reach are covered. The description adds that playlists are 'preview' (i.e., embedded/capped), which is useful, but it does not disclose the identity-resolution behavior or ambiguity handling when username/uri/url are omitted (0 required, none marked required in the description).

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 front-loaded sentences, no filler, and the disambiguation comes after the core purpose. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only fetch with an output schema and full parameter documentation, the description supplies the missing routing context (which sibling to use for followers, playlists, and search) and notes the preview semantics. Nothing an agent needs in order to call it correctly is absent.

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 each identifier and the 0-50 clamps. The description adds no format detail beyond what the schema provides, nor does it clarify the one-of relationship emphasized by the schema. Baseline 3 is appropriate.

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 and resource ('Fetch public Spotify profile metadata and preview playlists') and explicitly names the sibling tools it is not (spotify_profile_followers, spotify_profile_playlists, spotify_profiles_search). An agent can distinguish it from neighbors without inspecting 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use spotify_profile_followers or spotify_profile_playlists for dedicated lists, and spotify_profiles_search to find a profile. This is a textbook when-to-use / when-to-use-something-else statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?