Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

youtube_upload_video

Destructive

Upload a workspace-owned video file (file_id) to the connected YouTube channel. Returns video_id + thread_id. Costs 1600 quota units. Default privacy is 'private' — pass privacy='public' to publish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional list of tag strings (max ~500 chars total).
titleYesVideo title (max 100 chars).
file_idYesWorkspace `files.id` of the video to upload. Must be a video/* MIME type and `status='ready'`. Get IDs from the [ATTACHMENTS] block, files.search, or search.files.
privacyNoPrivacy status. 'private' (default), 'unlisted', or 'public'.private
category_idNoYouTube category ID (default '22' = People & Blogs). See https://developers.google.com/youtube/v3/docs/videoCategories/list.22
descriptionNoVideo description (max 5000 chars). OMIT to upload without a description.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
made_for_kidsNoCOPPA flag. OMIT for the standard (non-kids) default.
channel_account_idNoThe connected YouTube channel_account.id. OMIT to auto-resolve the workspace's YouTube account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / file_id / description
      Previous value: -"Workspace `files.id` of the video to upload. Must be a video/* MIME type and `status='ready'`. Get IDs from the [ATTACHMENTS] block, files.search, or workspace.search."New value: +"Workspace `files.id` of the video to upload. Must be a video/* MIME type and `status='ready'`. Get IDs from the [ATTACHMENTS] block, files.search, or search.files."
  5. Changed2 schema fields changed
    • changedInput schema / properties / channel_account_id / description
      Previous value: -"The connected YouTube channel_account.id (workspace-scoped)."New value: +"The connected YouTube channel_account.id. OMIT to auto-resolve the workspace's YouTube account."
    • changedInput schema / required
      Previous value: -[
-  "channel_account_id",
-  "file_id",
-  "title"
-]New value: +[
+  "file_id",
+  "title"
+]
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (non-readOnly, open-world, non-idempotent, destructive). The description adds genuine value beyond them: quota cost (1600 units), the default privacy behavior, and the return shape (video_id + thread_id). It does not disclose that re-uploading creates a new video rather than updating, but the added operational context is substantial.

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

Conciseness5/5

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

Four terse sentences, front-loaded with purpose, then returns, then cost, then the critical privacy default. Every sentence carries distinct information with no filler.

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

Completeness4/5

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

For a 9-parameter mutation tool with no output schema, the description supplies the return values, the quota cost, and the privacy default. Combined with full schema coverage and informative annotations, an agent has enough to call it correctly; only the lack of explicit alternative-tool routing keeps it from a 5.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all nine parameters, including file_id requirements, title/description limits, and category defaults. The description only restates the privacy default, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: upload a workspace-owned video file to the connected YouTube channel. The scoping ('workspace-owned', 'connected channel') clearly distinguishes it from siblings like youtube_update_video, youtube_list_videos, and tiktok_publish_video without requiring schema inspection.

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 actionable operational context: it costs 1600 quota units and defaults to private, with the explicit instruction to 'pass privacy=public to publish'. It lacks explicit when-not guidance or named alternatives (e.g., vs youtube_update_video), but the context is clear enough for correct usage.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources