Skip to main content
Glama

Search Yedapo episodes

search_episodes
Read-onlyIdempotent

Search Yedapo's 5,000+ AI summaries of podcast and YouTube episodes. Matches words in the episode title, the show name, the summary's topic tags and its short teaser text (not full transcripts). Returns up to 10 matches, newest first within each match type, each with show, date, teaser, the episode id for get_episode, and a page URL to cite. Newest summary added: 2026-11-18.

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": {
      "query": "<query>"
    },
    "name": "search_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWords to match against episode titles, show names, topic tags and teaser text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: a hard cap of 10 results, ordering ('newest first within each match type'), the exact payload of each match, and a data-freshness date, which is unusually useful context for judging result recency.

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?

Four dense sentences, front-loaded with scope, then matching semantics, then return shape, then freshness. Nothing is wasted or repeated; each sentence adds a distinct fact an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema present, the description fully compensates by describing the return shape (show, date, teaser, episode id, page URL), the result cap, and the ordering rule. Combined with the two-parameter schema and annotations, an agent has everything needed to call and interpret it.

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 query parameter is already fully described in the schema (100% of the required param), and the description largely restates those matching fields, adding only the 'not full transcripts' caveat. The undocumented limit parameter is only obliquely covered by 'Returns up to 10 matches', leaving the 1-10 range and its effect unclear at 50% schema coverage.

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?

States a specific verb (Search) and resource (5,000+ AI summaries of podcast and YouTube episodes), then enumerates exactly which fields are matched: title, show name, topic tags, teaser text. It also implicitly separates itself from get_episode by explaining that results carry 'the episode id for get_episode'.

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?

Clearly frames the tool as a discovery step feeding get_episode, and adds an explicit exclusion ('not full transcripts') that tells the agent not to rely on it for transcript search. It stops short of an explicit when-not-to-use statement or naming get_episode as the direct alternative for known-id lookups.

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