Content and publishing
AI agents that use YouTube
UtilitySpaces gives an AI agent scoped access to YouTube through its own encrypted connection, not your password. The agent can call 4 named YouTube tools, and the one that writes waits for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.
What an agent can do in YouTube
Read the connected channel's videos and statistics, and update a video's title, description, and tags. An agent calls these by name, and matching is exact.
| Tool | What it does | Waits for approval by default |
|---|---|---|
| List my channels | List channels owned by the connected account. | No — read only |
| Search my videos | Search the connected account's own videos. Costs 100 quota units per call against a 10,000/day default. | No — read only |
| Get video stats | Get a video's snippet and view/like/comment counts. | No — read only |
| Update video | Replace a video's snippet and status. This is a FULL REPLACE, not a patch: any snippet field you omit is cleared, and snippet.categoryId is mandatory. Read the video with get_video_stats first and send back everything you want kept. | Yes — it writes |
3 read tools, 1 write tool. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.
What teams hand an agent in YouTube
Content teams hand an agent the reporting on their own channel: pulling view, like, and comment counts with Get video stats and finding videos with Search my videos. Update video is the single write, it replaces the whole snippet rather than patching it, and it waits for a person unless this connection is set to run without asking.
- Keep a weekly performance recap current by reading stats for recent videos and comparing views and comments to the week before.
- Find the right video when someone in chat refers to it by topic, by searching the channel's own videos and linking the match.
- Update a video's title, description, and tags when a campaign or naming convention changes, sending back every field kept (after a person approves it)
What waits for a person
Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toYouTube, approved, rejected or unattended, is logged.
- Update video PUT
What connecting YouTube takes
YouTube uses OAuth, so you authorise in YouTube’s own screen and no secret is ever typed into UtilitySpaces. The connection asks for 1 scope, fixed in the catalogue and shown to you by YouTube before you agree:
- https://www.googleapis.com/auth/youtube.force-ssl
Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.
Where YouTube fits
Give an agent YouTube work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.
Other content and publishing integrations: Ghost. Or see every application agents can connect to.
See it doing your actual work
Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.
We reply to every message within one business day.