Google

YouTube

The dominant open video-distribution platform, with mature APIs for channels, videos, playlists, comments, captions, analytics, uploads, and push notifications.

Media generation, video & localizationSystem of productionExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of production
Access maturityExtensible SaaS
MCP supportDeveloper-context only
Reference updatedJun 1, 2026
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Channels, videos, playlists and items, subscriptions, comments and threads, captions, thumbnails, activities, live broadcasts and streams, and analytics-adjacent metadata.

02 · Data you can retrieve

Retrieve authorized/public video, channel, playlist, subscription, comment, caption, and live-streaming resources subject to quota and privacy rules.

03 · Actions and write paths

Upload, update, rate, moderate where supported, or delete videos; manage playlists, comments, captions, channel metadata, and live broadcasts/streams.

04 · Authentication and permissions

API keys identify projects for public-data requests; OAuth 2.0 scopes and user consent are required for private data and all insert, update, delete, or rating actions.

05 · Monitoring, approval, and recovery

Preserve creator identity, child-directed-content flags, rights and synthetic-media metadata, upload review, moderation policy, and quota/audit requirements.

06 · Limits and caveats

Every request consumes project quota; additional allocation requires a compliance audit, and periodic audits may be required to retain approved usage and continued access over time.

Agent access

MCP support

Developer-context onlyAdjacent Google developer-context MCP; no YouTube operational provider

Support: Developer-context only

Read scope: No first-party MCP read surface verified.

Write scope: No first-party MCP write surface verified.

Authentication: Not applicable to a first-party MCP provider.

Approval boundary: Require explicit channel-owner confirmation before upload, privacy changes, metadata replacement, comment moderation, rating, live-event mutation, or deletion; show the acting channel and projected quota cost.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access2
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Google ships them.

Single-platform patterns

  • Channel content and performance command center
  • Media production console
  • Localization and variant studio
  • Review-and-approval queue
Use in the brief builder →

Multi-platform compositions

  • YouTube + publishing or campaign platform: media production console
  • YouTube + DAM or CMS + social or video distribution system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
Platform core validationRepresentative source
https://developers.google.com/youtube/v3/docs ↗

Resource methods, API-key and OAuth boundaries, authenticated mutations, project quota, compliance audits, and private-upload restrictions

Publisher updated
Jun 1, 2026
BYO-UI reviewed
Jul 22, 2026

YouTube Data API authentication, mutations, upload restrictions, and quota audits reviewed 2026-07-22

Data APISource inventory
https://developers.google.com/youtube/v3 ↗

First-party API reference and guides.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer docsSource inventory
https://developers.google.com/youtube ↗

First-party developer documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.youtube.com/ ↗

Platform homepage.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.