Skip to main content
Glama
thenavidm

ScrapeCreators MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Playlist

spotify_playlist

Retrieve public Spotify playlist metadata and up to 50 tracks by ID or URL. Use the returned cursor for more tracks until null, with confirm=true for paid calls.

Instructions

Retrieves public Spotify playlist metadata and up to 50 tracks by playlist id or URL. For playlists with more tracks, pass the returned cursor into the next request until cursor is null. Potentially consumes paid API credits; requires confirm=true. Read-like POST requests do not publish to social platforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSpotify playlist id. If you'd prefer to use the URL instead, you can use the url parameter instead.
urlNoSpotify playlist URL. If you'd prefer to use the id instead, you can use the id parameter instead.
cursorNoCursor returned by the previous response. Omit it for the first page.
accountNoNamed private ScrapeCreators account; selects credentials, not a remote account ID.
confirmNoMust be true for the specific approved credit-consuming research call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Adds real context beyond the annotations: credit consumption, the confirm=true prerequisite, the pagination termination condition, and a clarification that a read-like POST does not publish to social platforms. This usefully explains why readOnlyHint=false despite non-destructive read semantics, though auth/token requirements and rate limits are not covered.

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: capability/scope first, then pagination and cost/confirm constraints. No filler, and every clause carries actionable information.

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

Completeness4/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 still discloses the payload shape (metadata plus up to 50 tracks), the pagination contract, and the credit/confirm gating. Missing only minor details such as behavior on private or unavailable playlists.

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 baseline is 3, but the description adds meaning to cursor (iterate with the returned value until it is null) that goes beyond the schema's 'omit for first page' note. The confirm and account parameters are left to their schema descriptions.

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 (retrieves) and resource (public Spotify playlist metadata + up to 50 tracks) with an explicit input mode (id or URL). It is clearly distinguishable from siblings such as spotify_track, spotify_album, spotify_artist, and spotify_search.

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?

Explains the repeated-call pattern precisely: pass the returned cursor until cursor is null, and states the id/URL entry options. It does not name when to prefer this over spotify_search or other Spotify siblings, so no exclusions or alternatives are given.

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