Skip to main content
Glama

Find videos and podcasts

discover
Read-onlyIdempotent

Find YouTube videos or podcasts on the open web (not limited to the indexed channels). type "youtube" returns videos; "podcast" returns shows with their RSS feed; "podcast_episode" returns individual episodes. Spotify-listed shows are found through their public RSS feed (Spotify-exclusive shows are not available). Next: ingest a result to transcribe it, or list_episodes on a show/channel.

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": "discover"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoyoutube
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
typeYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond them: results come from the open web, podcasts are resolved via public RSS feeds, and Spotify-exclusive shows are unavailable. Return-value detail is legitimately omitted because 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.

Conciseness4/5

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

Three compact sentences, front-loaded with the core purpose, then type semantics, then caveat and next steps. Every sentence carries information; only the slightly awkward inline quoting of enum values costs a point.

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 simple three-parameter discovery tool with an output schema and full annotations, the description covers purpose, type behavior, a key availability caveat, and follow-on actions. The one gap is any mention of result-count control via `limit`.

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 parameter meaning. It does a good job on `type`, spelling out all three enum behaviors, but says nothing about `query` (length bounds) or `limit` (1-20, default 10), leaving two of three parameters to the bare schema.

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 ("Find YouTube videos or podcasts") and immediately scopes it with "on the open web (not limited to the indexed channels)," which separates it from the indexed search sibling. An agent can tell this apart from search and list_channels without opening any schema.

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?

Explains what each type value selects and closes with an explicit next-step routing ("ingest a result to transcribe it, or list_episodes on a show/channel"), which is real when-to-use guidance. It lacks an explicit when-not-to-use versus the indexed `search` sibling, keeping it below a 5.

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