# How to connect YouTube public data to OpenClaw (paste one key, 17 tools) > Connect YouTube public data to OpenClaw with ClawLink: paste your YouTube public data key once and 17 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/youtube-data The usual route to YouTube public data access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical YouTube public data setup: install one ClawHub skill, connect YouTube public data in the browser, and OpenClaw can call real YouTube public data actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to YouTube public data. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect YouTube public data** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect youtube-data # connect YouTube public data (browser OAuth) npx -y @useclawlink/cli actions youtube-data # list available actions npx -y @useclawlink/cli run youtube-data --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect YouTube public data in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your YouTube public data account details once. Verify the connection by asking OpenClaw: > Use YouTube public data to youtubedata video info and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once YouTube public data is connected in the dashboard, that agent calls the same 17 YouTube public data tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## YouTube public data MCP for OpenClaw Looking for a YouTube public data MCP server for OpenClaw? ClawLink connects YouTube public data to OpenClaw and exposes 17 YouTube public data tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes YouTube public data integration](https://claw-link.dev/hermes/youtube-data) works the same way. ## What the OpenClaw YouTube public data integration can do 17 YouTube public data tools are ready for OpenClaw once the account is connected. ### All 17 YouTube public data tools for OpenClaw | Tool | What it does | |---|---| | **Video info** `youtubedata_video_info` | One video with stats | | **Video comments** `youtubedata_video_comments` | Comments on a video | | **Video captions** `youtubedata_video_captions` | Captions of a video as text | | **Channel info** `youtubedata_channel_info` | A channel's subscribers and description | | **Channel videos** `youtubedata_channel_videos` | A channel's recent uploads | | **Search videos** `youtubedata_search_videos` | Search videos by keyword | | **Search channels** `youtubedata_search_channels` | Search channels by keyword | | **Comment replies** `youtubedata_comment_replies` | Replies to a comment | | **Channel shorts** `youtubedata_channel_shorts` | A channel's Shorts | | **Channel playlists** `youtubedata_channel_playlists` | A channel's playlists | | **Playlist videos** `youtubedata_playlist_videos` | Videos in a playlist | | **Channel community posts** `youtubedata_channel_community_posts` | A channel's community posts | | **Community post** `youtubedata_community_post` | One community post | | **Search hashtag** `youtubedata_search_hashtag` | Videos with a hashtag | | **Trending shorts** `youtubedata_trending_shorts` | Trending Shorts | | **Video streams** `youtubedata_video_streams` | Playable stream URLs of a video | | **Channel contact email** `youtubedata_channel_contact_email` | A creator's business email | ## Example prompts **Youtubedata Video Info** > Use YouTube public data to youtubedata video info and walk me through the result in plain English. **Youtubedata Video Comments** > Use YouTube public data to youtubedata video comments and walk me through the result in plain English. **Youtubedata Video Captions** > Use YouTube public data to youtubedata video captions and walk me through the result in plain English. **Youtubedata Channel Info** > Use YouTube public data to youtubedata channel info and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual integration wiring plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want YouTube public data working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right YouTube public data credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link YouTube public data without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for YouTube public data. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right YouTube public data actions to the runtime in a format your agent can reliably use. | 17 tools for YouTube public data are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes YouTube public data to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect YouTube public data in the browser, and the 17 tools above work from chat. There is no SDK and no config file, and the YouTube public data key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the YouTube public data skill but can't call the tools The ClawHub skill teaches OpenClaw about YouTube public data, but the calls run through the ClawLink plugin and your connected account. Make sure YouTube public data is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect YouTube public data from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling YouTube public data tools YouTube public data tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every YouTube public data call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### YouTube public data returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for YouTube public data. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw YouTube public data integration? Yes. ClawLink is the fastest way to connect OpenClaw to YouTube public data: link your YouTube public data account once in the browser and OpenClaw can call the YouTube public data API through 17 ready-made tools — no custom code or token handling. ### How do I add YouTube public data to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink YouTube public data skill from ClawHub, then you click Connect in the dashboard to authorize YouTube public data. OpenClaw calls the tools from the next message — no config files, and the YouTube public data key you paste is stored server-side instead of in your environment. ### How long does it take to connect YouTube public data to OpenClaw? About two minutes. Sign in, click Connect next to YouTube public data in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring YouTube public data up myself? The alternative to ClawLink is usually manual integration wiring plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want YouTube public data working from chat. ### OpenClaw installed the YouTube public data skill but can't call the tools The ClawHub skill teaches OpenClaw about YouTube public data, but the calls run through the ClawLink plugin and your connected account. Make sure YouTube public data is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect Stack Exchange](https://claw-link.dev/openclaw/stack-exchange) — Search and browse questions, answers, and developer knowledge - [OpenClaw TikTok public data integration](https://claw-link.dev/openclaw/tiktok-data) — Read any public TikTok profile, video, comments, hashtag or search. Read-only and not your account: nothing to connect, paid per call from credit - [Connect X (Twitter)](https://claw-link.dev/openclaw/twitter) — Post tweets, manage lists, search content, and analyze engagement