podcasts

Search Episodes

search_episodes

Read-onlyIdempotent

Search indexed podcast episodes by keyword or show name and return the show/episode GUIDs needed for transcript retrieval.

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.	relevance
`limit`	No	Maximum number of episodes to return. Must be between 1 and 50.
`query`	No	Optional search keywords matched against indexed episode content. Use people, topics, companies, or phrases.
`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.
`podcast_name`	No	Optional podcast title or internal label to narrow results to a specific show.
`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.
`published_within_hours`	No	Filter episodes published in the past X hours. Maximum 168 hours (1 week).

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).

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds useful context by stating that the tool returns show/episode GUIDs needed for transcript retrieval, and that it searches 'indexed' content. However, it does not detail pagination, sorting behavior, or other operational nuances beyond what annotations already provide.

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 sentence of 21 words. It is front-loaded with the primary action and purpose, and every word contributes meaning. No redundancy or filler.

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?

Given the rich schema (8 params, all documented), output schema, and annotations, the description is sufficient for the tool's core function. It mentions the key return value (GUIDs) but does not explicitly mention that a query is optional or that it can list all episodes when no query is provided. Minor gap, but overall complete enough.

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 provides 100% coverage with descriptions for all 8 parameters, so the schema carries the heavy lifting. The description adds no parameter-specific meaning beyond the schema, only the overall purpose. This matches the baseline of 3 when schema coverage is high.

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 uses a specific verb ('Search'), states the resource ('indexed podcast episodes'), and specifies scope ('by keyword or show name'). It clearly distinguishes from siblings like search_episodes_by_topic by emphasizing keyword/show-based search, and highlights the end purpose (returning GUIDs for transcript retrieval).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when you need to find episodes by keyword or show name and obtain GUIDs for transcripts. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to infer appropriate usage. A sibling exists for topic-based search, though not referenced.

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.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool serves a distinct purpose: two different search methods (keyword vs. semantic), one for listing episodes, one for transcripts, and one for feedback. No ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.

Tool Count4/5

5 tools is on the lower end but appropriate for focused podcast episode retrieval and searching. Each tool has a clear role.

Completeness3/5

Covers core operations: listing, searching (two types), and transcript retrieval. Missing episode metadata details (title, date, description) which agents might need for user-facing tasks.

Resources

Need Help?