Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_artists_search

Search Spotify artists by keyword to retrieve matching profiles, including Spotify URIs, external URLs, and images, with offset and limit controls for paginated results.

Instructions

Search Spotify artists. Searches Spotify for artists matching a term, with offset and limit (1-50). Each artist has a title, Spotify URI, external URL and images. Matching artists are returned in both results and artists.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term
limitNoResult limit, clamped to 1-50
offsetNoSearch offset

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 must carry the behavioral load, and it does add real value: the returned fields (title, URI, external URL, images) and the quirk that matches appear in both `results` and `artists`. However it says nothing about pagination, total counts, auth, or rate limits, so coverage remains partial.

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 short sentences, front-loaded with the core action. The opening 'Search Spotify artists' is mildly redundant with the following sentence that repeats 'Searches Spotify for artists matching a term', but the whole is compact and readable.

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?

With no output schema the description sensibly sketches the return fields and dual result keys. For a search tool with no annotations it is adequate but leaves pagination behavior and the meaning of `offset` relative to result count unexplained.

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 q, limit and offset are already documented. The description only restates the limit clamp (1-50) that the schema already states, adding no new syntax or default semantics. 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 and resource ('Search Spotify artists') and clarifies it matches a term. An agent can distinguish it from generic spotify_search or spotify_tracks_search by the artist-noun, though the description never names those siblings explicitly.

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?

There is no when-to-use guidance, no condition distinguishing it from sibling searches (spotify_search, spotify_tracks_search, spotify_albums_search), and no prerequisites. Usage is only implied by the name.

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