Skip to main content
Glama

Fyyd Search Episodes

fyyd_search_episodes
Read-onlyIdempotent

fyyd, the open podcast directory, search individual podcast episodes, matching the term against episode titles and show-note descriptions, optionally filtered by language. Returns each episode's fyyd id, title, description, publication date, duration, audio enclosure URL and its parent podcast id. Answers which podcast episode covered a subject and where to listen to it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "artificial intelligence"
    },
    "name": "fyyd_search_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
pageNo
termYes
countNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 safety is covered. The description adds behavior beyond that: it discloses the match fields (titles and show-notes, not full transcripts or hosts) and the exact result fields returned, which tells the agent what a hit means. It does not mention pagination behavior, result caps, or empty-match handling, which keeps it short of a 5.

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 well-formed sentences, purpose front-loaded before the return-field list and the use-case clause. The enumerated return fields are somewhat redundant given a separate output schema exists, but the sentence is still readable and earns most of its space.

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

Completeness3/5

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

An output schema exists, so enumerating return fields is not strictly required, and the search-matching semantics are well covered. The real gap is that a paginated search tool with 'page' and 'count' parameters gives no hint about result-set size, paging behavior, or how broad a match set to expect — meaningful for an openWorld search.

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 0%, so the description must carry the burden. It adds real meaning for 'term' (matched against titles and show-note descriptions) and confirms 'lang' is an optional language filter, but 'page' and 'count' are never referenced, leaving pagination and result-size semantics completely undocumented.

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 and resource ('search individual podcast episodes' in 'fyyd, the open podcast directory') plus the matching scope (episode titles and show-note descriptions, optional language filter). This is clearly distinct from fyyd_search_podcasts, latest_episodes, and fyyd_get_podcast by resource granularity, so an agent can route without opening the schema.

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 closing sentence 'Answers which podcast episode covered a subject and where to listen to it' gives a concrete use case, which implies when to reach for this tool. However, it never names an alternative (e.g. fyyd_search_podcasts for shows, latest_episodes for browsing) or states any exclusion condition, so selection guidance is implied rather than explicit.

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.