Skip to main content
Glama
kaiding-ucb

podcast-summarizer-mcp

by kaiding-ucb

add_tracked_channel

Add a YouTube channel to your personal tracking registry to enable later summarization of its videos. Returns confirmation with the updated channel list.

Instructions

Add a channel to the registry. You MUST call this tool to add a channel — claiming "I've added X" without invoking it leaves the user's registry empty and the user has no way to know until they next ask "what am I tracking" and discover the missing channels.

Idempotent: re-adding the same channel_id updates name/handle/tags but preserves the original added_at timestamp. Tags are arbitrary strings — use them to group channels (e.g. ["macro"], ["semis", "podcast"]).

Args: channel_id: YouTube channel ID, must start with "UC". name: Display name (the user-friendly label). handle: Optional "@handle" (cosmetic, helps users identify the channel). tags: Optional list of grouping strings (default empty).

Returns: { added: true, channel: {channel_id, name, handle, tags, added_at}, registry_total: , registry_now_contains: [name, name, ...], # alphabetical user_facing_message: "Added X. Registry now has N channels: ..." } Use user_facing_message verbatim when telling the user the result — it carries the freshly-verified state and prevents misreporting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channel_idYes
nameYes
handleNo
tagsNo
Behavior5/5

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

Discloses idempotency behavior, constraint that channel_id must start with 'UC', and the return structure including user_facing_message. Since no annotations are provided, the description carries full burden and does so thoroughly.

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?

The description is structured but somewhat lengthy; however, each sentence provides essential information. It could be slightly more concise but remains effective.

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?

Given zero annotations and no output schema, the description covers behavioral details, parameter semantics, and return structure comprehensively. It even instructs the agent on how to present results.

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 description coverage is 0%, but the description details each parameter's purpose and constraints, such as channel_id format, handle being optional '@handle', and tags being arbitrary grouping strings. This adds significant value beyond the 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?

Clearly states 'Add a channel to the registry' and emphasizes that the tool must be invoked, distinguishing it from sibling tools like list_tracked_channels and remove_tracked_channel.

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?

Explicitly tells the agent to call this tool when adding a channel and warns against claiming addition without invocation. However, it does not provide explicit when-not-to-use or alternatives beyond the sibling context.

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