Skip to main content
Glama

captapi

by io.github.CDCStream
OverviewDiscussionsAdmin

spotify_podcast

Spotify podcast show — publisher, rating, topics, explicit flag, and totalEpisodes as clean JSON. Costs 1 credit. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesSpotify show/podcast URL, URI, or ID (e.g. https://open.spotify.com/show/…). Not an artist URL.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  2. Changed3 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "Max items to return. Default 20, max 50. Flat 1 credit per call.",
-  "minimum": 1,
-  "type": "integer"
-}
    • changedInput schema / properties / url / description
      Previous value: -"Spotify URL, URI, or ID. The URL platform must match this tool's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble."New value: +"Spotify show/podcast URL, URI, or ID (e.g. https://open.spotify.com/show/…). Not an artist URL."
  3. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 50. Flat 6 credits per call."New value: +"Max items to return. Default 20, max 50. Flat 1 credit per call."
  4. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 50. Billed per result."New value: +"Max items to return. Default 20, max 50. Flat 6 credits per call."
  5. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  6. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
+  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
+  "type": "boolean"
+}
  7. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden and does meaningful work: it discloses the 1-credit cost, states that empty results and failures are never charged, and explains the cache=true behavior (free 24h hit) versus the default always-fresh fetch. This is genuinely useful operational context beyond what the schema states. It does not mention rate limits or failure conditions, but for a simple read-only fetch tool the disclosed cost/caching behavior is strong.

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?

The description is three compact sentences with zero waste: purpose, cost/charging policy, and cache behavior. The core purpose is front-loaded in the first sentence, and each subsequent sentence carries distinct operational information. Every sentence earns its place.

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 2-parameter tool with no output schema, the description compensates well by enumerating the returned fields, substituting for the missing output schema, and by covering cost and caching semantics. The main gap is the absence of any differentiation from the sibling spotify_podcast_episodes tool, which an agent could easily confuse with this one.

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 the schema fully documents both `url` (with format, example, and a negative constraint) and `cache` (with credit semantics and default). The description's cache=true note largely restates what the schema already says, adding marginal value. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly identifies the resource (Spotify podcast show) and enumerates the specific output fields (publisher, rating, topics, explicit flag, totalEpisodes) delivered as clean JSON, which makes the tool's function unambiguous. It lacks an explicit verb like 'get' or 'fetch', though 'as clean JSON' strongly implies retrieval. Differentiation from siblings is implicit via the show-level field list rather than explicit naming.

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 field list implies the tool is for retrieving podcast show metadata, but the description gives no explicit when-to-use guidance or exclusions relative to closely related siblings like spotify_podcast_episodes or spotify_search. The 'Not an artist URL' constraint exists in the schema but not in the description, so the usage context is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All captapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources