Skip to main content
Glama

Fyyd Search Podcasts

fyyd_search_podcasts
Read-onlyIdempotent

fyyd, the open podcast directory, search podcast shows by title term, optionally restricted to a language code, up to 30 per page. Returns each show's fyyd podcast id, title, author, description, RSS feed URL, artwork and episode count. Answers which podcast shows exist under a name and where the RSS feed is.

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": "technology"
    },
    "name": "fyyd_search_podcasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoISO 639-1 language filter (e.g. en, de)
pageNo
termYes
countNo1-30 (default 10)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile needs no restating. The description still adds real value beyond them: search is limited to title terms (not full-text over descriptions), results are capped at 30 per page, and each record's payload is enumerated — the last point useful for selection even though an 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both doing work: the first carries purpose, parameters and limits; the second carries return shape and the question the tool answers. Nothing is repeated and the scope constraint is front-loaded.

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 four-parameter, read-only search with both annotations and an output schema, this is close to complete — an agent can decide to call it and construct a request. The only shortfall is the absence of explicit alternative-routing guidance among the many fyyd sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage at 50%, the description compensates well: it defines the meaning of term (title matching), lang (language restriction) and count ("up to 30 per page", which reinforces the schema's 1-30 bound). Only page is left without narrative explanation, and the pagination limit is at least implied.

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?

The description names a specific verb and resource ("search podcast shows by title term") plus the source directory, and finishes with a use-case framing ("which podcast shows exist under a name and where the RSS feed is"). It is clearly not episode search or a top-list tool, though it never names the sibling it should be chosen over.

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?

Usage context is implied by the phrasing about answering which shows exist under a name, and the tool's scope (title-term search, language restriction) points toward discovery queries. However, there is no explicit when-to-use or when-not guidance, and no routing to fyyd_search_episodes, fyyd_top_podcasts or fyyd_get_podcast for follow-up.

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.