Skip to main content
Glama

FoxAPIs data sources

Podcast page

podcast_episode
Read-onlyIdempotent

A podcast page on Apple Podcasts: show title, publisher and description, from its link. Costs 2 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "podcast_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFor example: "https://podcasts.apple.com/us/podcast/the-daily/id1200361736"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered; the description adds the commercially important details that the schema cannot: 2 credits per call, no charge for empty answers, and a required FoxAPIs key. It also states what content comes back, which is useful since no output schema exists.

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?

Two compact sentences with the resource and returned fields front-loaded, followed by cost and auth constraints. Nothing is redundant, though the opening fragment reads as a label rather than a complete clause.

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 single-parameter read tool with no output schema, the definition covers input source, returned fields, cost model, and auth prerequisite. Only the failure behavior for invalid or non-podcast URLs is left unaddressed.

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 coverage is 100% and the single `url` property already carries a concrete Apple Podcasts example. "From its link" confirms the parameter meaning but adds no format, validation, or edge-case detail 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?

"A podcast page on Apple Podcasts: show title, publisher and description, from its link" names the specific resource and enumerates the fields returned, which distinguishes it from other URL-based siblings like substack_post or appstore_app. It is a noun phrase rather than a verb+resource statement, so the action (fetch/retrieve) is only implied.

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 description gives no when-to-use guidance, no exclusions, and names no alternative tool for related lookups such as artist or publication pages. The only implied condition is that an Apple Podcasts URL is available, which the required parameter already conveys.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources