Crawlora MCP

spotify_profiles_search

Read-only

Search Spotify user profiles by searchTerm, returning users and a deduplicated results view. offset defaults to 0 and profile limit to 10, clamped to 1-50; inclusion flags request additional search context. Use spotify_profile for one profile's details or spotify_artists_search when searching for artists rather than user accounts.

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_profiles_search"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Result limit per section, clamped to 1-50, default 10.
`offset`	No	Search offset, default 0.
`isPrefix`	No	Treat the search term as a prefix when set.
`searchTerm`	No	Spotify catalog search term (required).
`includeAuthors`	No	Include author results when true.
`includeAudiobooks`	No	Include audiobook results when true.
`includePreReleases`	No	Include pre-release results when true.
`numberOfTopResults`	No	Top result limit, clamped to 1-50, default 5.
`includeAlbumPreReleases`	No	Include album pre-release results when true.
`includeArtistHasConcertsField`	No	Request Spotify artist concert-availability fields when true.
`includeEpisodeContentRatingsV2`	No	Include Spotify episode content ratings v2 when true.

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/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 the safety profile is covered. The description adds the deduplicated-results note and offset default, but the clamping detail simply repeats the schema, and 'inclusion flags request additional search context' is too vague to be actionable.

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 with the core purpose front-loaded and routing information last. No filler, though the middle sentence packs several loosely-related facts into one clause.

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 search with 11 fully-documented parameters and an output schema covering return values, the description supplies the purpose, key defaults, and sibling routing an agent needs. Nothing critical is missing.

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 all 11 parameters, including the required searchTerm the prose only alludes to. The description lumps the many inclusion flags into one generic phrase, adding little beyond the schema baseline.

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+resource ('Search Spotify user profiles by searchTerm') and explicitly distinguishes itself from two siblings, spotify_profile and spotify_artists_search. An agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Explicitly routes the agent to alternatives: spotify_profile for a single profile's details and spotify_artists_search for artists. It gives clear context for the substitute tools but does not spell out exclusions or edge conditions for using this search itself.

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?