Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

spotify_podcast

Fetch Spotify podcast details by providing a podcast ID or URL, returning show information for use in your application.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idNoSpotify podcast ID. Provide id or url.
urlNoSpotify podcast 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, the description must carry the behavioral load, and it does disclose a concrete credit-cost model: 1 credit on success, free for errors, blocked, timed-out, invalid requests and cache hits, with not-found billed per the operation's published cost. It adds nothing about what the response contains or whether authentication/credentials are required, so the disclosure is above minimum but incomplete.

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?

Purpose is stated first, followed by the input requirement and then cost behavior, so it is reasonably front-loaded. The leading "spotify: Podcast. GET /v1/spotify/podcast." boilerplate is redundant with the tool name but the cost sentence earns its length by preventing surprise charges.

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-optional-parameter lookup with no output schema and no annotations, the description covers identity and cost but never indicates what a podcast result looks like or how id vs url affect the response. It is sufficient to call the tool but leaves return-value expectations to inference.

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%, which sets a baseline of 3, but the description adds a real constraint beyond the schema: the schema declares zero required parameters, while the text says to supply one of id or url. That mutual-exclusivity/at-least-one requirement is genuinely new information for correct invocation.

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 gives a clear verb+resource ("Get Spotify podcast") and the underlying route GET /v1/spotify/podcast, so an agent knows it retrieves a single podcast entity. It does not distinguish itself from nearby siblings such as spotify_podcast_episodes, 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?

The only guidance is the input constraint "Provide one of: id, url", which is parameter-level, not usage-level. Nothing states when to choose this tool over spotify_podcast_episodes or other Spotify lookups, and there are no exclusions or preconditions.

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