Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Find music artists on SoundCloud and Spotify

find_music_artists
Read-onlyIdempotent

Search SoundCloud and Spotify by keywords or links to retrieve artist profiles with followers, contact details, releases, concerts and lead scores for A&R scouting, booking and outreach.

Instructions

Music artists from SoundCloud and Spotify by search words, artist links or playlist links: verified, independent or signed (from release label lines), followers, monthly listeners, top cities, latest releases, upcoming concerts, bio, website, Instagram, TikTok and YouTube links, public emails, and a lead score; optionally similar artists and their latest tracks with plays and likes. No login. Useful for A&R scouting, booking, music marketing and creator outreach. Runs the Apify Actor tacps126/media-profiles on your Apify account (about $0.0025 per artist, $0.001 per track; spend per call is capped at $0.5).

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": "find_music_artists"
  }
}

Input Schema

NameRequiredDescriptionDefault
linksNoArtist, track or playlist links on SoundCloud or Spotify.
queriesNoSearch words, e.g. ["lofi hip hop", "indie folk berlin"].
max_itemsNoMaximum results to return (default 50, max 1000). Cost scales with this.
platformsNoWhere to search (default both).
artist_typeNoKeep only these artists.all
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
max_followersNoMost followers.
min_followersNoFewest followers.
similar_artistsNoSimilar artists to add per artist found.
tracks_per_artistNoLatest tracks to add per artist (0 = profiles only).

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say read-only, open-world, idempotent; the description adds the operational facts an agent actually needs: no login required, execution on the user's Apify account, per-unit pricing ($0.0025/artist, $0.001/track) and a $0.5 per-call spend cap. The cost cap and auth model are exactly the sort of non-obvious behavior the annotations cannot convey.

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?

Front-loaded with the resource and sources, and every clause carries information (returned fields, cost, no login). It is a single very long run-on sentence with a dense field list, which costs some readability, but there is little genuine filler.

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?

Ten parameters, a nested object, and an output schema are all handled: the schema documents inputs, the output schema handles returns, and the description supplies the cost, auth, and spend-ceiling context an agent needs before invoking a paid scraping actor.

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%, so the schema carries the baseline. The description still adds meaning by explaining what the optional knobs produce in the result — similar artists and their latest tracks with plays and likes — which clarifies the purpose of similar_artists and tracks_per_artist beyond their terse schema text.

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 ('Music artists from SoundCloud and Spotify') plus the three retrieval modes (search words, artist links, playlist links). The domain (music artists) clearly separates it from siblings like find_companies or find_creators without needing their definitions.

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?

Names concrete use cases (A&R scouting, booking, music marketing, creator outreach) that tell the agent when this tool fits. It stops short of explicit exclusions or direct routing to an alternative sibling, so it is strong context rather than a full decision rule.

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