podcasts

Get Latest Episodes

get_latest_episodes

Read-onlyIdempotent

Return the most recent transcript-ready episodes across the full podcast catalog.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided.	published_desc
`limit`	No	Maximum number of episodes to return. Must be between 1 and 50.
`cursor`	No	Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results.
`published_after`	No	Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime.
`published_before`	No	Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Number of episodes returned on this page.
`episodes`	Yes	Matching transcript-ready episodes.
`next_cursor`	No	Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages.
`total_count`	Yes	Total number of matching transcript-ready episodes across all pages.
`total_count_is_approximate`	No	When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed6 schema fields changedJun 24, 2026

addedInput schema / properties / cursor

Added value: +{
+  "default": 0,
+  "description": "Zero-based episode offset for pagination. Use the `next_cursor` returned by a prior search/listing call to fetch the next page of results.",
+  "minimum": 0,
+  "type": "integer"
+}

changedOutput schema / properties / count / description

Previous value: -"Number of episodes returned."New value: +"Number of episodes returned on this page."

addedOutput schema / properties / next_cursor

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Cursor to pass to the next search call to retrieve the next page of results, or null if there are no more pages."
+}

addedOutput schema / properties / total_count

Added value: +{
+  "description": "Total number of matching transcript-ready episodes across all pages.",
+  "type": "integer"
+}

addedOutput schema / properties / total_count_is_approximate

Added value: +{
+  "default": false,
+  "description": "When true, `total_count` is a lower bound — more matches may exist than were counted. False for exact lexical/date counts; can be true only for semantic results (e.g. the topic-search fallback).",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "episodes",
-  "count"
-]New value: +[
+  "episodes",
+  "count",
+  "total_count"
+]

Changed6 schema fields changedMay 21, 2026

addedInput schema / properties / published_after

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Inclusive lower publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime."
+}

addedInput schema / properties / published_before

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Inclusive upper publication-date bound. Accepts YYYY-MM-DD or ISO 8601 datetime."
+}

addedInput schema / properties / sort

Added value: +{
+  "default": "published_desc",
+  "description": "Sort order for results. `relevance` ranks full-text searches first and falls back to newest-first when no query is provided.",
+  "enum": [
+    "relevance",
+    "published_desc",
+    "published_asc"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / episodes / items / properties / duration_seconds

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Episode duration in seconds when available from the source feed."
+}

addedOutput schema / properties / episodes / items / properties / rss_feed_url

Added value: +{
+  "description": "RSS feed URL for the podcast show.",
+  "type": "string"
+}

changedOutput schema / properties / episodes / items / required

Previous value: -[
-  "show_guid",
-  "show_title",
-  "episode_guid",
-  "episode_title",
-  "published_date",
-  "description"
-]New value: +[
+  "show_guid",
+  "show_title",
+  "episode_guid",
+  "episode_title",
+  "published_date",
+  "rss_feed_url",
+  "description"
+]

First observedApr 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, which already establish the safety profile. The description adds that episodes are 'transcript-ready' and span the 'full podcast catalog,' clarifying the scope and quality filter. It does not contradict annotations and adds useful context.

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 a single, concise sentence that front-loads the action and resource. No wasted words; it is appropriately sized for the tool's simplicity.

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?

The description, combined with rich schema parameter descriptions, annotations, and an output schema, provides adequate context for most use cases. It doesn't explicitly mention the relevance sort option or search alternatives, but the overall information is sufficient for a listing tool.

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?

The input schema has 100% coverage, with descriptions for all 5 parameters, so the baseline is 3. The description does not add any parameter-specific detail beyond the schema, so no additional credit is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns the most recent transcript-ready episodes across the full catalog, using a specific verb ('Return') and resource ('episodes'). It distinguishes from siblings like search_episodes by focusing on 'latest' and 'full catalog' rather than query-based search.

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 description implies this is for retrieving recent episodes, but it does not explicitly say when to use it over siblings like search_episodes or search_episodes_by_topic. There is no explicit exclusion or alternative reference, so usage guidance is only implied.

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

All podcasts tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?