Skip to main content
Glama
JCodesMore

YouTube for AI Agents

by JCodesMore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

youtube_clip

Extract multiple clips from a YouTube video by specifying start and end timestamps. Downloads source once, then cuts each clip, optionally creating a highlight reel.

Instructions

Extract one or more clips from a YouTube video by timestamp. Downloads the source video once at 720p, then cuts each clip. Each clip needs startTime and endTime (seconds, MM:SS, or HH:MM:SS) and an optional label for the filename. Uses fast keyframe-aligned cuts by default — do NOT set accurate: true unless the user explicitly asks for frame-perfect precision (it re-encodes and is much slower). Keep clips tight — 5-10 seconds each, capturing one key moment per clip. When 2+ clips are provided, automatically produces a per-video highlight reel alongside individual clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipsYesOne or more clip definitions with start/end timestamps
forceNoBypass the duration guard for long videos
qualityNoVideo quality for the source download (default: best)
videoIdYesYouTube video ID
accurateNoFrame-accurate cuts via re-encoding — MUCH slower. Only use when the user explicitly needs frame-perfect precision. Default fast keyframe cuts are fine for nearly all use cases (default: false)
outputDirNoOutput directory for clip files (defaults to current directory)
highlightReelNoCombine all clips into a single highlight-reel video (default: true). Set to false for individual clips only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Adds valuable context beyond annotations, such as the 720p default, keyframe-aligned cuts, re-encoding behavior of accurate:true, and the automatic highlight reel generation for 2+ clips. Annotations are sparse, so this additional detail is important.

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-structured and front-loaded: starts with the core action, then explains mechanics, parameter formats, and defaults. No wasted sentences, each clause adds useful information.

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?

Complete for a tool with this complexity and no output schema. It covers mechanics, parameter formats, defaults, and important behavioral traits, leaving little ambiguity for an agent.

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?

Describes clip parameters (startTime, endTime, label) and their formats, and explains accurate and highlightReel semantics. Schema coverage is 100%, so this adds some value but mostly repackages schema details with a bit more context.

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 (Extract clips) and resource (YouTube video by timestamp), and the mechanism is clear: download once at 720p, cut each clip.

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?

Gives explicit guidance on when to use accurate:true vs default and advises keeping clips tight at 5-10s. Does not compare against sibling tools like youtube_download or youtube_highlight_reel, but the internal usage guidance is strong.

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

Deploy Server

Other Tools