YouTube Transcripts, Comments & Channel Analytics
Discussions
Channel comparisons: a weekly row is a snapshot, not a reconstructed past week For readers comparing a known list of YouTube channels, keep the observation date and the recent-upload scope with the numbers. A new row does not tell you what an unobserved past week looked like. Our existing channel-statistics guide explains a weekly n8n example that calls YouTube Channel Analytics and appends dated rows to a Google Sheet. It does not discover competitors, backfill weeks, calculate week-over-week changes, or deduplicate repeated appends. Missing values need review, and source-rounded subscriber counts can hide small changes. The same section distinguishes YouTube-specific Channel Analytics from the separate cross-platform Social Blade Scraper. The weekly example calls the former only; optional Social Blade enrichment is not a call to the separate scraper. An estimated earnings range is not a creator's actual income. Guide: https://github.com/LMSlay/tubetext-examples/blob/main/n8n/README.md#channel-statistics-weekly-youtube-competitor-tracking-in-google-sheets I maintain TubeText, and this note was prepared with AI assistance. This is an existing documentation resource, not a live test or an MCP-to-n8n integration. Reading it requires no connector run. Templates are free to download; optional Actor execution and connected services can incur charges. Check current inputs and pricing before running.
A reported lesson lookup trial: evidence and remaining checks For readers evaluating combined YouTube search and captions, we have published a short case note about new public feedback in Nous issue #508: https://github.com/LMSlay/tubetext-examples/blob/main/recipes/nous-youtube-lesson-trial-note.md The repository maintainer reported three captions-only runs of the underlying YouTube Actor on Apify's Free plan. Each returned six transcripts; reported wall times were 9.7–12.4 seconds and the reported charge was $0.02405 per run. These are the maintainer's observations, not a benchmark we reproduced or a fixed price for future requests. We have not independently inspected the run logs, raw results or billing records. The useful remaining check is separate from successful retrieval: the maintainer requires exhausted allowance to produce an explicit diagnostic instead of an empty search. That is a migration requirement, not behavior verified as implemented here. Their migration remains planned; the previous provider is still in production. The case note links the original report and decision, with both their dates and limitations. Disclosure: I maintain TubeText, and this post was prepared with AI assistance. This is an Actor trial report, not a test of this MCP connector or proof of its health. The note is freely readable. New Actor or connected-service use can incur charges; the reported Free-plan trial is not a promise of free runs, future coverage or performance. No paid conversion or production adoption has been established.
Glama MCP Gateway
Add one secure layer between your agents and this server.
Maintainer resource note (TubeText; AI-assisted): If you use video text as research evidence, first separate a generated discovery answer from the caption passage you actually selected. Our existing checklist covers retaining the video link/ID, actual language, available caption timing/source information, and collection date. Unknown fields stay unknown. Keep your interpretation separate and return to the recording for important quotations. Guide: https://github.com/LMSlay/tubetext-examples/blob/main/recipes/ask-youtube-and-retained-caption-sources.md This is a documentation-based reading guide, not a live test or an Ask YouTube integration. Reading it does not require running this MCP connector; native YouTube feature availability follows YouTube’s terms. Optional TubeText/Apify extraction is separately billed. Check the connector’s current health independently.