Skip to main content
Glama
Upload-Post

Upload-Post

Official

Read YouTube

youtube_read
Read-only

Read YouTube channel data from a connected Upload-Post account, including videos, playlists, comments, captions, analytics, and live streams for monitoring and reporting.

Instructions

Read-only YouTube data of the connected channel. Fields go in params with the API's names; lists page with max_results and page_token. videos (ids up to 50, parts, include_owner_details: status, processing, statistics, translations); quota (the account's allowance left today); rating (ids: the channel's like/dislike); playlists (ids or channel_id), playlist_items (playlist_id), playlist_image (playlist_id); captions (video_id: caption tracks); comments (video_id, or scope: channel for the whole channel; moderation_status published|heldForReview|likelySpam, order, search, include_replies), comment_replies (parent_id); search (q, for_mine, channel_id, type video|channel|playlist, order, published_after…; few searches per day: free plan 1, paid 5), categories (region), languages, regions; channel (settings, branding, translations, statistics), channel_lookup (for_handle, ids), channel_sections, subscriptions (filter mine|my_subscribers), activities; broadcasts (status active|upcoming|completed), broadcast (broadcast_id), streams, stream (stream_id; include_stream_key returns the secret key to the owner), live_chat (broadcast_id or live_chat_id, page_token; wait polling_interval_ms between reads), super_chats. Every call spends the account's daily YouTube allowance (free plan 200 units, paid plans 2,000; resets at midnight Pacific time; youtube_read quota shows what is left): reads cost about 1 unit, most writes 50, captions 400-450, so batch reads and avoid needless writes.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "youtube_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
userNoUpload-Post profile name with YouTube connected (not needed for quota and catalogs).
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavior beyond them: per-call quota costs (1 unit reads, 50 writes, 400-450 captions), the 200 vs 2,000 daily allowance, midnight Pacific reset, pagination via max_results/page_token, and the fact that include_stream_key returns a secret key. These are exactly the constraints an agent needs before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded correctly and nearly every clause carries information, but the body is one long semicolon-separated run-on with no line breaks or grouping, which makes scanning 24 actions slow. The quota-cost sentence at the end is valuable but repeats allowance figures stated in the middle of the block.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the description still covers what the schema cannot: which action takes which fields, quota economics, pagination, polling, and secret-key exposure. The 'user' parameter is documented in the schema itself, so nothing material is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The params object is free-form (additionalProperties with no per-field schema), so the description carries nearly the entire semantic burden and does so well: it names each action's fields, enum values (moderation_status published|heldForReview|likelySpam, type video|channel|playlist, status active|upcoming|completed), the 'ids up to 50' limit, and date filtering with published_after. Coverage is 67% at the schema level and the description compensates for the free-form blob, though field shapes for less common actions are terse.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and scope ('Read-only YouTube data of the connected channel') and then enumerates all 24 actions with their distinguishing fields, so an agent can tell exactly what this tool covers versus the manage_youtube_* siblings. The action vocabulary is concrete (videos, captions, live_chat, super_chats) rather than generic.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real operational guidance: search is capped at 1/day on free plans and 5 on paid, live_chat reads require polling with a wait interval, and callers should batch reads because of quota cost. What is missing is explicit routing to siblings for the write counterparts (manage_youtube_videos, manage_youtube_comments), which is only implied by 'avoid needless writes' and the read-only framing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools