Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

spotify_album

Fetch Spotify album data by ID or URL to resolve album metadata for integrations. Provide either identifier and receive structured album results.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idNoSpotify album ID. Provide id or url.
urlNoSpotify album URL. Provide id or url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description does carry meaningful behavioral weight by spelling out the cost model: 1 credit on success, free for errors, timeouts, invalid requests and cache hits. That is genuinely useful, but it says nothing about what an album record contains, whether auth is needed, or what a failed lookup returns, so the full disclosure burden is not met.

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 constraint sentence is front-loaded and useful, but two of the five sentences are boilerplate pricing policy (free errors, cache-hit pricing, not-found charging caveat) that dilutes the tool-specific content, and the opening line duplicates the tool name and route.

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?

For a simple two-parameter read lookup with no output schema and no nested objects, the description covers the input requirement and the billing behavior, which is most of what an agent needs. The remaining gap is the absence of any hint about what the album response contains or how a not-found appears.

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 would be 3, but the description adds a real constraint the schema does not encode: the schema has zero required properties and additionalProperties=false, so it technically permits neither or both arguments, while the description clarifies exactly one of id or url must be supplied.

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?

"Get Spotify album" gives a specific verb plus resource, and the resource (album) is clearly separable from siblings like spotify_track, spotify_artist, and spotify_playlist. The leading "spotify: Album. GET /v1/spotify/album" fragment merely restates the name and route without adding scope, so it stops short of a 5.

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, not usage guidance. Nothing tells the agent when to reach for spotify_album versus spotify_track or the apple_music equivalents, and there are no prerequisites or exclusions stated.

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