Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

spotify_playlist

Retrieve a Spotify playlist and its tracks by providing a playlist ID or URL, with cursor pagination for paging through results.

Instructions

spotify: Playlist. GET /v1/spotify/playlist. Provide one of: id, url. Get a Spotify playlist and its tracks Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
idNoSpotify playlist ID. Provide id or url.
urlNoSpotify playlist URL. Provide id or url.
cursorNoCursor returned by the previous response. Omit it for the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: the credit-cost model, including that failures, cache hits and invalid requests are free. However, it says nothing about authentication, rate limits, pagination behavior implied by the cursor parameter, or the shape of the returned playlist data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The useful content ('Get a Spotify playlist and its tracks') is front-loaded, but it is preceded by two lines of boilerplate that restate the tool name and HTTP route. The cost paragraph is long and partly redundant with the operation's own published pricing.

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?

For a read-only retrieval tool with no annotations and no output schema, the description covers cost and input selection but leaves the return value undefined — an agent cannot tell what a 'playlist and its tracks' response contains or how pagination continues. Adequate but with clear gaps.

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 all three parameters are already documented, including the 'provide id or url' rule and the cursor semantics. The description merely restates the id/url alternative and adds no meaning about the cursor or pagination beyond the schema.

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?

The sentence 'Get a Spotify playlist and its tracks' states a specific verb and resource, and the endpoint line confirms it is a retrieval of a playlist object plus its track listing. It does not explicitly distinguish itself from siblings like spotify_album or spotify_track, but the resource is unambiguous.

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?

'Provide one of: id, url' is a parameter constraint that the schema already states verbatim, not when-to-use guidance. Nothing tells the agent when to choose this over spotify_track or youtube_playlist, and there are no stated prerequisites or exclusions.

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