Skip to main content
Glama

captapi

by io.github.CDCStream

youtube_transcript

YouTube's published captions with timestamps — not speech-to-text. Flat 1 credit; 404 is free. Costs 1 credit. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic YouTube video URL, e.g. https://youtube.com/watch?v=ID. Not a TikTok/Instagram/Facebook URL. The URL platform must match this endpoint's platform. Do not pass cross-platform URLs, e.g. YouTube to TikTok, Instagram to Facebook, LinkedIn to X/Twitter, or Pinterest to Rumble.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
languageNoPreferred caption language as an ISO code, e.g. "en". Defaults to auto-detect.

TDQS

A3.8/5.0
Behavior4/5

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

No hay anotaciones, por lo que la descripción asume toda la responsabilidad de transparencia. Aporta información útil sobre costos ('Flat 1 credit; 404 is free'), ausencia de cargos por fallos/resultados vacíos, y comportamiento de caché ('Pass cache=true for a free 24h cache hit'). Falta mencionar detalles como el formato exacto de retorno o posibles límites, pero cubre bien los aspectos clave de comportamiento.

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?

La descripción es breve (tres frases) y va al grano: primero define qué es, luego el costo y finalmente el comportamiento de caché. No hay relleno y cada oración contribuye a la comprensión del funcionamiento de la herramienta.

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?

La herramienta tiene 3 parámetros, no tiene output schema ni anotaciones. La descripción cubre el tipo de datos, el costo, el manejo de errores y el caché. Sería más completa con una nota sobre el formato de respuesta o una referencia a alternativas para otras plataformas (p.ej., video_transcript), pero en general es suficiente para un uso correcto.

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?

La cobertura del esquema es del 100%, por lo que el baseline es 3. La descripción no añade significado adicional a los parámetros: el parámetro 'cache' ya se explica en el schema ('0 credits on hit') y la descripción solo repite esa información. No aporta contexto nuevo sobre 'url' o 'language'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Descripción comienza con 'YouTube's published captions with timestamps — not speech-to-text', identificando claramente el recurso (subtítulos publicados de YouTube) y el formato (con marcas de tiempo). Diferencia de speech-to-text, aunque no distingue explícitamente de hermanos como youtube_shorts_transcript o video_transcript.

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

Usage Guidelines3/5

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

La frase 'not speech-to-text' proporciona una indicación de cuándo no usar esta herramienta, sugiriendo que otras herramientas (como youtube_audio_transcript) son para audios transcritos. Sin embargo, no se nombran alternativas explícitas ni se dan reglas claras de selección entre los múltiples transcriptores de la lista de herramientas hermanas.

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

All captapi toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation3/5

The platform-prefix convention keeps most of the 178 tools clearly separated, but several clusters are genuinely ambiguous: tiktok_live_info is explicitly described as 'Identical to TikTok Live', instagram_basic_profile and instagram_channel_details both return profile stats, and facebook_profile_posts overlaps with facebook_profile_reels. The generic 'Summarizer' descriptions for facebook_summarize, instagram_summarize, and tiktok_summarize provide no disambiguating detail at all.

Naming Consistency4/5

The dominant snake_case platform_resource_suffix pattern is followed remarkably consistently across 178 tools (e.g. youtube_channel_videos, tiktok_search_users, reddit_subreddit_posts). Minor deviations exist: the same creator resource is called 'channel' in some tools (tiktok_channel_details, instagram_channel_posts) but 'profile' or 'user' in others (facebook_profile_posts, twitch_user_videos, linnkme_profile); link-in-bio tools mostly use _page but linkme uses _profile; and the video_summarize/video_transcript pair lacks a platform prefix.

Tool Count2/5

At 178 tools this is far beyond what any agent can efficiently navigate in a single flat namespace, and even individual platform subsets exceed reasonable bounds (TikTok alone has ~34 tools, YouTube ~25). The sheer breadth of the multi-platform scope partially justifies the count, but the server would be far more usable split into per-platform servers.

Completeness4/5

The read-only data surface is impressively thorough: nearly every platform has profile + content + search + comments coverage, and TikTok, YouTube, Instagram, and Facebook are covered end-to-end including shops, ads, transcripts, and summaries. Notable gaps are minor: Twitter has no keyword search tool, LinkedIn lacks comments, and Reddit has no user-profile endpoint, but none of these create dead ends for the server's core data-retrieval purpose.

Resources