Skip to main content
Glama
kaiding-ucb

podcast-summarizer-mcp

by kaiding-ucb

discover_new_videos

Find new YouTube videos from tracked channels, skipping livestreams and short clips. Returns newest uploads since last check, with optional tag filtering.

Instructions

Discover new videos from YouTube channels since the last time this MCP saw them.

Two modes for selecting channels:

  1. Pass channel_ids explicitly (legacy behavior).

  2. Omit channel_ids and the MCP reads from its tracked-channel registry (managed by add_tracked_channel / remove_tracked_channel). Use tag to filter the registry — e.g. tag="macro" returns only channels tagged macro.

State is tracked per channel in a server-managed JSON file. On the FIRST call for a channel, the most recent video is returned (and state is seeded) so the caller has something to analyze without ingesting the entire backlog.

Filters applied:

  • Livestreams (duration == 0) are skipped

  • Videos shorter than min_duration_seconds are skipped (default 10 minutes)

  • Videos older than or equal to the last-seen video are skipped

Args: channel_ids: Optional list of YouTube channel IDs. If omitted, the registry is used. tag: Optional tag filter for registry-based mode (ignored if channel_ids given). max_per_channel: How many recent uploads to inspect per channel (default 5) min_duration_seconds: Minimum video length to include (default 600 = 10min)

Returns: DiscoverResult with new_videos (newest first), skipped, channels_processed, and first_run_channels (channels that had no prior state).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idsNo
tagNo
max_per_channelNo
min_duration_secondsNo
Behavior5/5

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

No annotations present, but description fully discloses state tracking, filters (skip livestreams, short videos, old videos), and first-run behavior. No contradictions.

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?

Well-organized with sections for modes, state, filters, args, and returns. Each sentence adds value; no redundancy. Front-loaded with core purpose.

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?

Complex tool with 4 params, state management, filtering, and two modes. Description covers all aspects: inputs, behavior, output fields. Sufficient without output schema.

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

Parameters5/5

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

Schema coverage is 0%, but description explains all 4 parameters: channel_ids, tag, max_per_channel, min_duration_seconds, including defaults and conditional behaviors.

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?

Clearly states the tool discovers new videos from YouTube channels since last seen, with two modes and filtering. Distinguishes from siblings like search_youtube_channels or get_video_info which serve different purposes.

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

Usage Guidelines5/5

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

Explicitly explains two modes: explicit channel_ids vs registry-based, and tag filter. Also describes first-call behavior and mentions related tools for registry management.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kaiding-ucb/podcast-summarizer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server