Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

spotify_track

Retrieve Spotify track metadata by providing a track ID or Spotify song URL, returning track details for lookup and verification through the Fetchproof API.

Instructions

spotify: Track. GET /v1/spotify/track. Provide one of: id, url. Get Spotify track 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_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoSpotify track ID. Provide id or url.
urlNoSpotify song URL. Provide id or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 behavioral burden. It does valuable work by disclosing the credit cost model in detail (1 credit on success; errors, blocked, timed-out, invalid, and cache hits free), which is real behavior beyond structure. But it says nothing about authentication needs, rate limits, or what the response contains, leaving meaningful gaps for a lookup tool.

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 core information is front-loaded, but the opening repeats itself ('spotify: Track. GET /v1/spotify/track ... Get Spotify track') and the trailing cost sentence about not-found results is dense boilerplate. The pricing caveat is long relative to the useful content conveyed.

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 simple two-parameter read tool this covers identification input and billing, which is the most agent-relevant context. There is no output schema, so the description arguably should hint at the returned track shape, and it omits auth and response-format information needed to fully anticipate the result.

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. The description adds meaning the schema does not encode: the schema makes both id and url optional with no constraint, while the description states 'Provide one of: id, url', conveying the required one-of relationship between the two identifiers.

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 description names the resource (Spotify track) and the operation (get), and by naming itself 'spotify_track' alongside siblings like spotify_album/spotify_artist it is reasonably distinguishable. It does not explicitly state the distinction, and 'Get Spotify track' restates the name, but the combination of verb, resource, and endpoint makes the intent unambiguous.

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

Usage Guidelines3/5

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

The line 'Provide one of: id, url' gives concrete invocation guidance about how to identify the track. However, there is no when-to-use guidance, no mention of when to prefer this over sibling tools such as apple_music_track or a search tool, and no exclusions or prerequisites.

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