Klyf
Server Details
AI YouTube analyst in Claude for creators: audit, fix, decide what to make next, grow subs.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- Klyf
TDQS
Scored across 25 tools
Most tools target clearly distinct dimensions (audience, single video, comments, ideas, packaging, drafts, channel admin), and descriptions aggressively cross-reference each other ('for X use Y') to steer selection. The weak spot is a cluster of whole-channel analysis tools — audit_channel, diagnose_channel, check_growth, get_weekly_digest — whose boundaries are only held apart by long prose rather than by obviously separate actions, so an agent can still hesitate between them.
Every one of the 25 tools uses the same snake_case verb_noun pattern (analyze_audience, draft_script, find_best_videos, reply_to_comment, switch_channel). No camelCase, no bare nouns, no stray verbs. Highly predictable.
25 tools sits right at the heavy end of the range for a YouTube analytics/assistant server. Each has an identifiable job, but the analytics cluster (audit, diagnose, growth, weekly digest, best videos, discoverability) could plausibly be consolidated into fewer entry points without losing capability.
The surface covers the whole creator loop: diagnose, discover, growth, audience, per-video analysis, comment reading and replying, idea generation, evaluation, packaging, scripting, description drafting, pre-publish review, and limited write-back to video metadata. Minor gaps remain — no thumbnail upload, no scheduling/publishing, and write access limited to title/description/tags — but agents can work around these.
Available Tools
25 toolsanalyze_audienceARead-onlyInspect
Analyze WHO the signed-in user's YouTube audience is, from their own channel's real data: age and gender of viewers, top countries and where viewers are, and what that means for their content. Call this for ANY question about WHO their viewers are, however phrased: who is my audience; who watches or is watching my channel or videos; who are my viewers or subscribers; who am I reaching or serving; tell me about, describe, or help me understand my audience; what is my audience like; my audience demographics; how old are my viewers or what age range; are my viewers male or female or the gender split; where are my viewers or subscribers from; what countries watch me; my geography or location breakdown. Always the user's own audience, never a competitor's. For HOW people find the channel, whether new people are discovering it, search terms, or reach and the algorithm, use check_discoverability; for what the audience SAYS, wants, or struggles with (from their comments), use read_comments; for what to make next, use evaluate_idea. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
analyze_videoARead-onlyInspect
Deep dive on ONE specific YouTube video of the signed-in user's own channel, to explain how it did and why. Returns that video's performance versus their usual, where viewers dropped off, how it was found, and what its comments say. Call this whenever the user asks about a SINGLE video: how a video did or performed, why a video flopped, bombed, tanked, underperformed, or got few views, why a video did well, blew up, popped off, or went viral, what happened with a video, or to break down, analyze, review, or explain one video. Also for 'my last video', 'my latest video', 'my newest upload', or a video named by its title. If the user names the video (a title or part of one), pass it as video; leave video empty to analyze their most recent upload. A vague reference with no title (like 'that video', 'this video', 'the video') also means their most recent upload: analyze it, do not stop to ask which one. For the whole channel at once use audit_channel; for the ranked list of what to fix use diagnose_channel; for the best videos across the channel use find_best_videos. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: title, video.
audit_channelARead-onlyInspect
Give the signed-in user a full audit and overview of THEIR OWN YouTube channel in one answer: the overall state right now, what is working and why, which single thing is constraining the channel (whether people are not being SHOWN the videos or are being shown and not clicking), and what their audience wants. This is the broad front-door command, and it reads the channel as a whole. For a ranked list of which VIDEOS to fix first and in what order, call diagnose_channel instead. Call it when the user asks to audit, analyze, review, assess, evaluate, or check their channel; wants a channel overview, health check, summary, or the big picture; or asks broad questions like 'how is my channel doing', 'what is going on with my channel', 'analyze my channel', or 'give me my channel overview'. ALWAYS pass ask: 'broad' when they asked to audit/review/analyze the channel or how it is doing overall, 'specific' when they asked for the channel read but aimed it at ONE thing (an audit focused on their titles, a review that only cares about packaging). Pass refresh: true ONLY when they explicitly want the numbers re-pulled rather than the last saved read (they say it is out of date, or they just published and want it counted); it is slower and Klyf Pro only. This is a SNAPSHOT of right now: for anything about direction over time (is it growing or sliding, why growth stalled, is this month better than last) call check_growth instead, or first, since a snapshot cannot see a trend and will contradict it. Always about the user's own connected channel, never a competitor's. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: ask, refresh.
check_discoverabilityARead-onlyInspect
Diagnose how the signed-in user's own YouTube channel gets FOUND, and whether new people are finding it at all. Returns whether their views come from people who already subscribe or from new viewers discovering them, through which door people arrive (search, suggested, browse, external), and the actual searches already bringing them viewers, with the one thing to change to get discovered more. Call this for reach and discovery, however phrased: why am I not getting discovered or found, how do I get found or rank in search, why isn't the algorithm pushing / recommending / suggesting my videos, how do I reach new people or grow beyond my current subscribers, am I only reaching people who already follow me, what searches or keywords bring people to my videos, how do people find me, where does my traffic come from, how do I get more reach or discovery. Pass video (a title or part of one) to zoom into ONE upload and diagnose whether THAT video's problem is reach (few people find it) or conversion (people find it but do not subscribe), through which door it is found, and the searches that found it: use this when the user asks why a SPECIFIC video is not getting found, discovered, recommended, or reaching new people, or whether a video's problem is reach or getting subscribers. Always the user's own channel. For WHO the audience is (age, gender, location), use analyze_audience; for a single video's overall performance, why it flopped, or where viewers dropped off, use analyze_video; for the ranked list of videos to fix, use diagnose_channel. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: title, video.
check_growthARead-onlyInspect
Whether the signed-in user's own YouTube channel is growing, sliding, or flat, and roughly when it turned, from recent views, watch time, and net subscribers. Call this for growth, momentum, or trajectory: is my channel growing or dying, going up or down, gaining or losing steam, getting better or worse, is this month better than last. ALSO call it for WHY questions about growth: why is my channel not growing, why am I not growing, why has my growth stalled or slowed down, why is my channel stuck. Those need the real direction FIRST, because the premise is often wrong and a snapshot alone contradicts what the trend shows. But the direction alone does not answer WHY: this tool holds no packaging, retention, reach or comment data, so for a why-question also call audit_channel (with ask 'specific') and answer with the direction and the cause together. For the current-state overview use audit_channel; for one video use analyze_video. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
diagnose_channelARead-onlyInspect
Diagnose the signed-in user's YouTube channel. Returns a ranked, prioritized list of which videos to fix first, at which funnel stage (packaging, retention, or audience fit), and what each is costing. This is the core Klyf tool; call it when the user asks what to fix or improve on their channel. It is a per-VIDEO worklist: for what the channel is about, who it serves, and the one constraint holding it back, call audit_channel instead. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
draft_descriptionARead-onlyInspect
Draft a YouTube video DESCRIPTION for the signed-in user, in their own voice and structure (learned from the descriptions they already write). Call this when the user asks to write, draft, rewrite, or improve a video description, or the text/notes/blurb under a video. Pass video to improve an existing upload's description, or idea for a new video, plus title when a title has already been agreed. This is for the description text only; for titles and thumbnails use package_video.
Inputs: idea, title, topic, video, +1 more.
draft_scriptARead-onlyInspect
Draft a video SCRIPT for the signed-in user, in their own voice, built from what already converts on their own YouTube channel and engineered to fix the opening where they lose viewers. For a long-form video it returns two or three hook options, a beat-by-beat outline, key lines, a CTA, and a suggested title; for a Short, a tight word-for-word script. Call this when the user asks to write, draft, or outline a script (or a hook, intro, or outline) for a video or idea. Pass topic (what the video is about) and optionally format ('short' or 'long'). Klyf Pro only. For titles and thumbnails use package_video; to judge whether an idea is worth making use evaluate_idea; to brainstorm ideas use suggest_ideas.
Inputs: idea, title, topic, format.
enable_auto_replyAInspect
Start turning on auto-reply (Klyf posting the YouTube comment replies the user approves on their own channel). Call this when the user asks to enable or turn on auto-reply, asks how to let Klyf post replies for them, OR asks Klyf to reply to / respond to / answer their comments for them or to 'do it for me'. It handles the plan and permission automatically: returns the upgrade link if they are not Pro, the one-time permission link if they are Pro but have not granted it, or confirms it is already on. Prefer this over posting when the user has not yet enabled auto-reply.
Inputs: no named parameters.
evaluate_ideaARead-onlyInspect
Judge whether a specific YouTube video idea, topic, or title the user is weighing up is worth making, grounded BOTH in what already converts on their own YouTube channel and in how that topic actually performs for other channels YouTube places next to theirs: roughly what a decent video on it gets, what the best get, and whether the demand is still current. Call this whenever the user proposes an idea and asks whether it (or a title) is worth making, will work, or is a good idea, and also when they ask what a topic or subject normally gets, how big a topic is, whether a topic is worth their time, or how their channel compares to others covering it. For deeper packaging help (several title options, thumbnail text, or reviewing/scoring a title or thumbnail), use package_video instead.
Inputs: idea, title, topic.
find_best_thumbnailsARead-onlyInspect
Read what the signed-in user's BEST-performing YouTube thumbnails on their own channel have in common (the on-thumbnail text, faces, colors, layout), to reveal the pattern behind their proven packaging. Call this when the user asks what makes their best thumbnails work, what their winning thumbnails share, or wants to understand their thumbnail pattern. This is only about the pattern ACROSS their top thumbnails. To generate or score packaging for a specific or new video (title options, thumbnail text, or reviewing one video's title/thumbnail), use package_video. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
find_best_videosARead-onlyInspect
Find the signed-in user's best-performing YouTube videos on their own channel, ranked several ways: which produced the most subscribers, the most views, held viewers longest (retention), earned the most total watch time, got clicked most often when shown, and which sparked the most comments, with their titles, so the pattern behind what works becomes clear. Call this when the user asks what is working, which videos performed best, what got them subscribers, which video had the best retention or held viewers longest, which got the most watch time, which video or thumbnail got the most clicks or the best click-through rate, which video got the most comments, what their winners have in common, or what to make more of. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
find_videosARead-onlyInspect
SEARCH the signed-in user's own YouTube catalogue and LIST the videos that match, by what is written in their titles, descriptions and tags. This is RETRIEVAL, not ranking: call it whenever the user wants to FIND or LIST videos rather than judge them. Use it for 'which of my videos are about X', 'show me every video where I talked about X', 'find my videos mentioning X', 'which videos have a referral or affiliate link in the description', 'list all my videos', 'what have I made about X', or any question whose answer is a SET of their videos. Also use it to pull ONE video's full record (its complete description, tags, length, views): pass that video's title as video. Leave everything empty to browse the whole library newest first. Results are paginated: each answer says how many matched and the offset to pass to see the next page, so keep asking to walk a large catalogue rather than stopping at the first page. It searches only what the creator WROTE, never what is spoken in the video. For how a video PERFORMED use analyze_video; for the best performers use find_best_videos. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: after, limit, query, title, +4 more.
get_weekly_digestARead-onlyInspect
Klyf Pro. The creator's week in review for their own YouTube channel: what changed this week versus last (views and subscribers), the video that stood out, the one thing to fix, and a comment worth answering, ending with one action for the week. Call this when the user asks for their weekly digest or summary, what changed or happened this week, how their week went, their week in review, or to catch them up on the channel. For a point-in-time overview use audit_channel; for direction over months use check_growth. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
list_channelsARead-onlyInspect
List the YouTube channels this creator has connected to Klyf, and say which one Klyf is currently working with. Call this when the user asks which channels they have connected, which channel Klyf is using or answering about, whether Klyf can see their other channel, or how many channels they have on Klyf. This lists the channels connected TO KLYF, which is not the same as every channel on their Google account: Klyf cannot see those. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: no named parameters.
package_videoARead-onlyInspect
Help the signed-in user PACKAGE a YouTube video: generate several title options and thumbnail text ideas, or score a title/thumbnail they already have, always as a title+thumbnail UNIT (making sure the two complement and do not just repeat each other), grounded in the packaging that already converts on their own YouTube channel. Call this whenever the user wants help with a title or a thumbnail, wants title options or thumbnail text, asks to package or repackage a video, or wants their title/thumbnail reviewed, scored, or improved. Pass video to package or critique an existing upload of theirs (by its title), idea to generate packaging for a new idea or topic, BOTH video and idea for a follow-up or sequel to one of their videos (the new video's packaging, grounded in the one it follows), and/or title/thumbnail_text to score ones they paste. For judging whether an idea is worth making at all, use evaluate_idea; to brainstorm video ideas from scratch, use suggest_ideas; for the general pattern across their best thumbnails, use find_best_thumbnails.
Inputs: idea, title, topic, video, +1 more.
read_commentsARead-onlyInspect
Read and summarize the audience's YouTube comments for the signed-in user's channel: the themes viewers keep raising or asking for, what the audience wants, needs, struggles with, or their pain points and problems (as voiced in comments), and how many comments are unanswered. Call this when the user asks what their audience wants or struggles with, what people are saying or commenting about, what themes come up, or about unanswered comments. Pass video (a title or part of one) when they ask about ONE upload's comments, like 'what are people saying on my IBKR video' or 'any questions on my latest tutorial'; omit it for the whole channel. For WHO the audience is (age, location, how they find you), use analyze_audience; for what video to make next, use suggest_ideas. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: title, video.
read_comment_threadARead-onlyInspect
Read the full reply thread under one YouTube comment on the signed-in user's channel: the original plus the whole back-and-forth, so you can reply in context. Call this BEFORE drafting a reply to ONE specific comment that has replies (marked [THREAD] in read_comments) and to see whose turn it is in an ongoing conversation. Do NOT call this for a general question about what people are saying or the themes across their comments; that is read_comments only. Only open a thread when you are actually about to reply to one specific comment. Use the comment's id (the 'lc=' value from its reply link). Part of Klyf Pro's reply flow.
Inputs: comment_id (required).
reply_to_commentAInspect
Post a reply to one specific YouTube comment on the signed-in user's channel, on their behalf. ONLY call this after you have shown the user the exact reply text and they have explicitly approved posting it. It is a Klyf Pro feature and needs the user's one-time write permission; if they lack either, it returns the link they need. Use the comment's id from read_comments (the value after 'lc=' in that comment's reply link).
Inputs: comment_id (required), reply_text (required).
review_upcoming_videoARead-onlyInspect
Review a YouTube video the signed-in user is ABOUT to publish on their own channel (a scheduled, unlisted, or private/draft upload of theirs, NOT one already public) and give them a prioritized punch-list of what to fix before it goes live: title and thumbnail versus what works on their channel, the description, key settings, and the best time to publish (from when their own uploads have done best and where their audience is). Call this when the user wants to get an upcoming, scheduled, draft, or unlisted video ready, reviewed, checked, or prepared before release or publishing; asks 'is my next video ready', 'what should I fix before I publish', 'review my video for tomorrow', 'get my upload ready', or asks what time or when to publish or post it. Pass video (a title or part of one) to pick a specific upcoming upload; omit it to review the most imminent one. For a video that is ALREADY public use analyze_video; for titles and thumbnails alone use package_video. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: title, video.
submit_feedbackAInspect
Send feedback, a bug report, or a feature request to the Klyf team. If the user reports a specific problem or makes a specific request, even in one line (like 'the audit crashed on my last video' or 'let me export my winners to a spreadsheet'), send it right away this turn with kind set to bug, feature, or general; you can still ask a follow-up after. Only when the complaint is too vague to categorize (like 'something is wrong' or 'Klyf doesn't work' with no specifics) ask one short follow-up to pin down what happened, then send. A bug report about a Klyf tool (like a crashed audit) is feedback to log here, not a request to run that tool.
Inputs: message (required), kind.
suggest_ideasARead-onlyInspect
Generate specific video ideas for the signed-in user's own YouTube channel to make next, grounded in what already earns them subscribers there (their winners), what their audience keeps asking for (their comments), and what each suggested subject is actually worth: roughly what videos on it earn for channels YouTube places next to theirs, so the ideas can be ranked by real headroom rather than by hunch. Call this when the user asks what to make, film, or post next; for video ideas, content ideas, or topic suggestions; what their next video should be; to brainstorm ideas; or says they are out of ideas or stuck on what to make. This GENERATES ideas from scratch. To judge or package a specific idea the user already has in mind, use evaluate_idea instead. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: subjects.
switch_channelAInspect
Change which of the creator's connected channels Klyf works with, so every later answer is about that channel. Call this when the user asks to switch, change or use a different channel, to look at another one of their channels, or names one of their own channels and asks about it instead. Takes the channel name as the user says it. Use list_channels first if you do not know what they have connected. Needs no input: it reads their real connected YouTube channel directly. Never ask the creator anything first, not for context, not for a link, not for a title you could look up; call it immediately.
Inputs: channel (required).
update_video_detailsADestructiveInspect
Apply a title, description and/or tags to one of the signed-in user's own YouTube videos. ONLY call this after you have shown the user the exact wording and they have explicitly approved it, the same way you would before posting a comment reply. NEVER write the wording yourself and apply it in one step. Pass only the fields being changed; anything you omit is left exactly as it is. Call it with just video and no other field to see what Klyf has already changed on that video and what the values were before, which is how you put something back. Klyf Pro, and needs the user's one-time write permission; if they lack either it returns the link they need.
Inputs: video (required), tags, title, description.
upgrade_to_proAInspect
Give the signed-in user a link to upgrade to Klyf Pro. Call this whenever the user asks to upgrade, subscribe, go Pro, pay, unlock Pro or paid features, remove limits, or asks how to get auto-reply or other Pro-only capabilities. Pass interval 'year' when the user asks for the annual, yearly, or discounted plan; otherwise leave it monthly.
Inputs: interval.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Your YouTube library in Claude, ChatGPT and Cursor: transcripts, breakdowns, summaries, search.
Your YouTube library in Claude, ChatGPT and Cursor: transcripts, breakdowns, summaries, search.
AI content strategist for YouTube, X, Instagram and Threads creators: what to post, outliers, hooks.
126 AI video editors for Claude: raw phone take in, finished Reel, TikTok or Short out.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI-powered YouTube content management using Claude Code to orchestrate research, scripting, and scheduling via Google Sheets, Docs, and Drive.-
- AlicenseNot gradedqualityDmaintenanceManages YouTube channels via Claude Desktop, enabling AI-powered metadata optimization, video scheduling, playlist management, and backups with safety guardrails.MIT
- AlicenseNot gradedqualityBmaintenanceConnects Claude to the YouTube Data API and YouTube Analytics API so it can pull any public channel's profile, uploads, comments and stats, compare channels side by side, and read a channel owner's private analytics like retention curves, traffic sources, audience demographics and subscribers per video. Changes to your own video titles, descriptions and tags are previewed and require approval, with responses cached locally to save API quota.MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to directly analyze YouTube channel performance by fetching real metrics such as views, watch time, retention, traffic sources, reach/CTR, and comments via YouTube APIs.-
Glama MCP Gateway
Add one secure layer between your agents and this server.