Skip to main content
Glama
Achanandhi-M

youtube-watch-mcp

by Achanandhi-M

Check for new YouTube uploads

check_new_videos

Check YouTube channels on your watchlist for recently published videos. Omit channel parameter to check all watched channels.

Instructions

Check watched channel(s) for videos published since the last check. Omit 'channel' to check everyone on the watchlist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNoNickname or channel ID to check; omit to check all watched channels
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It mentions 'since the last check' indicating statefulness but fails to clarify whether it is read-only, required authentication, or if repeated calls have side effects. For a tool with zero annotation coverage, this is insufficient.

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?

Single sentence of 12 words, front-loaded with purpose, no filler. Every word earns its place.

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?

For a simple tool with 1 optional parameter and no output schema, the description provides essential functionality but lacks usage guidelines and behavioral transparency (e.g., statefulness implications, return format). It is adequate but not complete.

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 coverage is 100% with a description that already covers omitting the parameter. The description adds no significant new meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the tool checks watched channels for videos published since the last check, with specific verb and resource. It also explains how to use the optional parameter to check all channels, distinguishing it from the get_latest_videos sibling which likely returns current latest without state tracking.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like get_latest_videos. The description implies it's for incremental updates but does not compare with siblings or specify prerequisites.

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/Achanandhi-M/youtube-watch-mcp'

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