Skip to main content
Glama
Sign In
YouTube Channel MCP

YouTube Channel MCP

by joinhackyard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Cut a vertical Short

create_short

Cuts a seconds-based start/end segment from a local video into a vertical 1080x1920 MP4 for YouTube Shorts (max 180s), with crop, blur, or original layouts; requires ffmpeg.

Instructions

Cuts start-end (seconds) from a local video into a vertical 1080x1920 MP4 for YouTube Shorts (max 180 s). layout crop fills the frame from the centre (talking heads); blur shows the whole frame over a blurred fill; original keeps the aspect ratio. Needs ffmpeg.

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": {
      "file_path": "<file_path>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "create_short"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
layoutNocrop
file_pathYes
overwriteNoReplace output_path if it already exists.
output_pathNoWhere to save; default is the shorts folder in the data directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world operation; the description adds real context beyond them: an external ffmpeg dependency, the 1080x1920 MP4 output format, and a 180 s duration ceiling. It does not say what happens when the requested span exceeds 180 s or how long processing takes, which is the main remaining behavioral gap.

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?

Three tight sentences, front-loaded with the core action and output, then option meanings, then the prerequisite. Every clause carries information; nothing is redundant with the title.

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?

With no output schema, the description covers input expectations, output format, and the ffmpeg prerequisite well enough to call the tool. The notable omission is what the tool returns (presumably the written file path) and failure behavior at the 180 s limit.

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?

Schema coverage is only 33% (just overwrite and output_path), so the description must carry weight, and it does: start/end are explicitly in seconds, file_path is a local video, and all three layout enum values are explained with their visual effect. The layout explanation in particular adds meaning the bare enum cannot.

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: cuts a start-end segment from a local video into a vertical 1080x1920 MP4 for YouTube Shorts. This is clearly distinct from siblings like suggest_shorts (ideas), extract_frames (stills), and upload_video (publishing).

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 clear context for use (producing a YouTube Short from local footage, capped at 180 s) and even maps layout choices to scenarios (crop for talking heads). It stops short of naming alternatives or stating when not to use it, e.g. versus suggest_shorts or upload_video.

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