Skip to main content
Glama

срезAI — MCP-сервер и поисковый API для ИИ-агентов

Субтитры YouTube / YouTube transcripts

yt_srt
Read-onlyIdempotent

Забирает текстовую дорожку ролика YouTube - ручные субтитры или авто - по ссылке или 11-символьному id. Видео и звук не скачиваются: это дешёвый способ получить содержание ролика в контекст агента.

Когда: нужен текст видео - конспект, цитата, проверка сказанного, поиск по содержанию лекции; ролик уже известен или найден через web_search. Для поиска видео используйте web_search (например, site:youtube.com), а не этот тул. Когда не: нужен текст страницы - read_url; нужна картинка/вёрстка - fetch_page; не YouTube (VK, Rutube, Дзен) - не работает. Плейлист не разбирается, нужен ролик. Возвращает по каждому ролику: название, канал, длительность, дату, язык, вид дорожки (ручные/авто), текст и ссылки на ролик и канал. Если дорожки нет - статус и список доступных языков: повторите с существующим. Длинный текст приходит окном maxChars; в конце указано from, с которым надо вызвать тул, чтобы получить продолжение без повторной оплаты. Цена: 1 кредит за ролик, у которого субтитры получены; неудачи (нет дорожки, ограничение частоты, недоступный ролик) не списываются. До 5 роликов за вызов.

Fetches a YouTube video's text track - manual captions or auto - by URL or 11-char id. No video or audio is downloaded: this is the cheap way to bring video content into the agent's context.

Use when: you need the text of a video - a summary, a quote, checking what was said, searching a lecture; the video is known or was found via web_search. To find videos use web_search (e.g. site:youtube.com), not this tool. Do not use when: you need page text - read_url; you need layout or a screenshot - fetch_page; the video is not on YouTube. Playlists are not expanded, pass a video. Returns per video: title, channel, duration, date, language, track kind (manual/auto), the text and links to the video and channel. If no track exists - a status plus the list of available languages, so you can retry with a real one. Long text arrives in windows of maxChars; the end states the from value for the continuation call, already-read text is not charged again. Cost: 1 credit per video whose captions were fetched; failures (no track, rate limiting, unavailable video) are not charged. Up to 5 videos per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoКонец окна в секундах. / Window end in seconds.
fromNoНачало окна в секундах (для продолжения используйте next_from из ответа). / Window start in seconds (use next_from from the response for continuation).
videosYesСсылки на ролики YouTube или их id (до 5 за вызов). Формы: watch?v=, youtu.be/, shorts, embed, live, голый 11-символьный id. / YouTube video URLs or ids (up to 5 per call).
maxCharsNoСколько символов текста вернуть на ролик (200-50000, по умолчанию 12000). / Characters of text per video (200-50000, default 12000).
languagesNoЯзыки в порядке предпочтения, по умолчанию ["ru", "en"]. Ручная дорожка предпочтительнее авто. Если нужного языка нет - вернём доступные. / Languages in preference order, default ["ru", "en"]. Manual tracks are preferred over auto; if the requested one is missing, available ones are returned.
timestampsNotrue - вернуть фрагменты с таймкодами вместо сплошного текста (дороже по контексту; для навигации по длинному ролику). / true - return timestamped fragments instead of continuous text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/open-world safety, and the description goes well beyond them: credit cost (1 credit only for videos whose captions were actually fetched), failure non-charging, the 5-video batch cap, the maxChars windowing plus from/next_from continuation that is not re-charged, and the no-track fallback that returns available languages. These are exactly the operational traits an agent needs before calling.

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?

Each paragraph is front-loaded and purposeful (purpose, use/do-not-use, returns, cost), and every sentence carries distinct information. The main cost is that the entire text is duplicated in Russian and English, roughly doubling the payload for identical content.

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?

With no output schema, the description fully carries the return-shape burden: per-video title, channel, duration, date, language, track kind, text and links, plus the no-track status path. Cost, batching and pagination semantics are all present, leaving nothing an agent needs to call it correctly.

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 description coverage is 100% and every parameter (to, from, videos, maxChars, languages, timestamps) is already documented with ranges and defaults, so the baseline is 3. The description reinforces the maxChars window and continuation workflow but adds no syntax or format detail the schema lacks.

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 ('Fetches a YouTube video's text track - manual captions or auto - by URL or 11-char id') and immediately bounds the scope with 'No video or audio is downloaded'. An agent can distinguish it from read_url, fetch_page and web_search without opening any schema.

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?

Explicit 'Use when' / 'Do not use when' blocks with named alternatives: web_search for finding videos, read_url for page text, fetch_page for layout/screenshot, and a stated limitation (non-YouTube platforms, playlists not expanded). This is close to a routing table for the sibling set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.