Home / Token cost / Youtube

The Youtube MCP server costs 6,533 tokens before the first call.

Connect Youtube and its 36 tool definitions are loaded into the model's context on every request — 3.3% of a 200k window spent before your agent does anything.

QUICK ANSWER The Youtube MCP server's tool definitions consume 6,533 tokens — 3.4× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 36 tools · 6,533 tokens · 3.3% of 200k · 0.7% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 3.3%
1M WINDOW 0.7%

Corpus context: Youtube ranks #930 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 6,533 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 181 tokens per tool.

ToolCategoryTokens% of server
youtube_search Read 414 6.3%
YOUTUBE_LIST_PLAYLIST_ITEMS Read 413 6.3%
YOUTUBE_GET_CHANNEL_ACTIVITIES Read 341 5.2%
YOUTUBE_UPDATE_VIDEO Write 338 5.2%
YOUTUBE_SEARCH_YOU_TUBE Read 321 4.9%
YOUTUBE_UPLOAD_VIDEO Write 317 4.9%
YOUTUBE_GET_VIDEO_DETAILS_BATCH Read 306 4.7%
YOUTUBE_LIST_CHANNEL_VIDEOS Read 259 4.0%
YOUTUBE_VIDEO_DETAILS Read 245 3.8%
youtube_list_comments Read 222 3.4%
YOUTUBE_LIST_USER_SUBSCRIPTIONS Read 204 3.1%
YOUTUBE_LOAD_CAPTIONS Read 184 2.8%
youtube_list_subscriptions Read 175 2.7%
YOUTUBE_UPDATE_THUMBNAIL Write 174 2.7%
youtube_get_popular_videos Read 173 2.6%
YOUTUBE_LIST_USER_PLAYLISTS Read 170 2.6%
YOUTUBE_LIST_CAPTION_TRACK Read 167 2.6%
youtube_get_video Read 149 2.3%
youtube_list_comment_replies Read 149 2.3%
youtube_list_playlists Read 149 2.3%
youtube_list_playlist_items Read 147 2.3%
YOUTUBE_GET_CHANNEL_STATISTICS Read 143 2.2%
youtube_get_channel Read 141 2.2%
youtube_list_video_categories Read 140 2.1%
youtube_add_playlist_item Write 115 1.8%
youtube_create_playlist Write 115 1.8%
youtube_update_playlist Write 114 1.7%
YOUTUBE_SUBSCRIBE_CHANNEL Read 105 1.6%
youtube_post_comment Write 96 1.5%
YOUTUBE_GET_CHANNEL_ID_BY_HANDLE Read 95 1.5%
youtube_rate_video Destructive 92 1.4%
youtube_remove_playlist_item Destructive 92 1.4%
youtube_reply_comment Write 73 1.1%
youtube_update_comment Write 71 1.1%
youtube_delete_comment Destructive 62 0.9%
youtube_delete_playlist Destructive 62 0.9%

Most agents use a handful of these tools. They pay for all 36.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (181 tokens each).

Grant scopeDefinition costReduction
All 36 tools (no gateway) 6,533 tokens
3 granted tools ~544 tokens −92%
5 granted tools ~907 tokens −86%
10 granted tools ~1,815 tokens −72%

Youtube token-cost questions.

How many tokens does the Youtube MCP server use?+

Its 36 tool definitions total 6,533 tokens — 3.3% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Youtube consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Youtube's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Youtube to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 544 tokens, a 92% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 36 catalogued Youtube tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Youtube to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.