Skip to main content
Glama
Hermoso

Hermoso

Official

Post a video to YouTube

post_to_youtube
Destructive

Upload a video or Short to a brand's connected YouTube channel, setting title, description, privacy, thumbnail, and schedule. It publishes publicly by default; choose unlisted for ads.

Instructions

Use this when the user wants to upload a video or Short to YouTube. Publishing costs no credits. Publish a finished video to the brand’s connected YouTube channel. Pass a Hermoso render URL (or an upload_file url for a local/external file). PUBLISHES PUBLICLY BY DEFAULT: a plain "post this to YouTube" puts it ON the channel (confirm the title with the user, as for any publish) and notifies subscribers as YouTube does. Pass the privacy the user states instead: "unlisted" (link-only) or "private" (eyes-only). A video meant to run as a YouTube/Google AD should go up "unlisted" — private videos CANNOT be used as ads. Never choose unlisted for music on your own. Needs a connected YouTube channel (Connectors > YouTube). Full rules: get_instructions({topic:'post_to_youtube'}).

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": {
      "videoUrl": "<videoUrl>"
    },
    "name": "post_to_youtube"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoWHAT ANGLE this post is built on, recorded only at publish time. post_performance ranks hooks on it (a winner needs 5 posts sharing ONE hook), so pass a list_hooks id (e.g. "direct_callout", "before_after") or reuse your own wording EXACTLY across a campaign. Omit it and this post never votes on which hook works.
tagsNoup to 30 tags
brandNoWHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted.
titleNoREQUIRED in practice — the headline every search result and the Shorts feed shows (≤100 chars); an upload with no title is refused
ideaIdNoshort id of the content-plan idea this post came from
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
accountNoWHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the profile has more than one youtube account connected (several and none named is refused by name, never guessed); omit when there is one.
licenseNoYouTube licence: youtube (standard) or creativeCommon
privacyNodefault public (live + searchable on the channel); unlisted = link-only (the ad-ready setting, or to add YouTube music in Studio first — only when the user asks); private = eyes-only (cannot run as an ad)
subjectNoWHAT THIS POST IS ABOUT — product, feature, offer or theme (e.g. "winter coat", "free trial"). post_performance's second grouping axis: reuse the exact wording, as with hook.
videoUrlYesthe video to post — a Hermoso render URL or an upload_file url; a URL, not a local file path; use upload_file for local files
coverAtMsNoTHE VIDEO COVER (the custom thumbnail), as ONE frame: milliseconds from the start (7000 = the frame at 7s). That frame is cut from the upload and set with thumbnails.set. thumbnailUrl wins; this beats platformCover.
publishAtNoSCHEDULE the publish — ISO 8601, e.g. "2026-09-01T15:00:00Z", and it must be in the future. YouTube only allows this on a PRIVATE video and makes it PUBLIC at that moment, so pass privacy:"private" (or leave privacy unset) — asking for a scheduled "unlisted" or "public" post is refused rather than half-honoured.
categoryIdNoYouTube category id, NUMERIC — default "22" (People & Blogs), which is wrong for most ads. 1 Film & Animation · 2 Autos & Vehicles · 10 Music · 15 Pets & Animals · 17 Sports · 19 Travel & Events · 20 Gaming · 22 People & Blogs · 23 Comedy · 24 Entertainment · 25 News & Politics · 26 Howto & Style · 27 Education · 28 Science & Technology · 29 Nonprofits & Activism. The assignable set is region-specific, so the value is forwarded as given and YouTube has the last word.
embeddableNotrue = allow embedding on other sites
playlistIdNoadd it to this playlist (list_youtube_playlists)
aiGeneratedNoYouTube’s “altered or synthetic content” declaration (containsSyntheticMedia). OMIT IT and Hermoso decides from provenance: a Hermoso render is declared, a video the user uploaded through upload_file or from an external URL is NOT — real footage must not carry the label. true/false overrides.
descriptionNoREQUIRED in practice — what the video shows, a line about the brand, a link and a few #hashtags (≤5000 chars); YouTube search, suggested videos and the Shorts feed rank on it, so an upload with no description (and no caption) is refused
madeForKidsNodeclare the video MADE FOR KIDS (COPPA) — default false; YouTube then turns off comments and personalised ads
brandPartnerNosponsoring brand's channel id (UC…) or @handle — gives that brand access to run the video as a partnership ad; "" unlinks (update only)
firstCommentNofirst comment as the channel (≤2,000)
thumbnailUrlNothe custom thumbnail: a Hermoso-hosted image (make_thumbnail, or upload_file for the user’s own). Omit it and a representative frame of the video is set, free; "auto" keeps YouTube’s pick. Custom thumbnails need a verified channel.
localizationsNotranslated title/description per language, e.g. {"es":{"title":"…"}}; needs defaultLanguage
platformCoverNoVIDEO COVER. Omit it (the default) and Hermoso sets the video’s best frame — the same frame as its Library thumbnail — as the cover (YouTube custom thumbnail; the same as thumbnailUrl:"auto" when true). true = send no cover and let the platform pick (usually the first frame). A cover you pass yourself always wins.
recordingDateNoYYYY-MM-DD
defaultLanguageNolanguage of title/description, e.g. "en"
notifySubscribersNoTHE DEFAULT FOLLOWS PRIVACY. privacy:"public" NOTIFIES the channel's subscribers — that is YouTube's own default and normally what someone publishing publicly wants. privacy:"unlisted" and "private" do NOT: the video is not on the channel, so announcing it is nonsense, and a blast to somebody's whole subscriber list cannot be undone. A scheduled publish (publishAt) is PRIVATE at upload, so it does not notify either — pass true to announce one. An explicit value ALWAYS wins in both directions: true announces an unlisted/private upload, false publishes publicly and quietly. The reply reports which way it went and why.
publicStatsViewableNotrue = show public view and like counts
defaultAudioLanguageNospoken language, e.g. "es"
paidProductPlacementNotrue = contains PAID product placement (sponsored) — YouTube shows the disclosure; legally required for sponsored content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.571
    • addedInput schema / properties / firstComment
      Added value: +{
      +  "description": "first comment as the channel (≤2,000)",
      +  "type": "string"
      +}
    • addedInput schema / properties / playlistId
      Added value: +{
      +  "description": "add it to this playlist (list_youtube_playlists)",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.1.532
    • addedInput schema / properties / madeForKids
      Added value: +{
      +  "description": "declare the video MADE FOR KIDS (COPPA) — default false; YouTube then turns off comments and personalised ads",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changedv0.1.525
    • changedInput schema / properties / videoUrl / description
      Previous value: -"the video to post — a Hermoso render URL or an upload_file url"New value: +"the video to post — a Hermoso render URL or an upload_file url; a URL, not a local file path; use upload_file for local files"
  4. Changed9 schema fields changedv0.1.465
    • addedInput schema / properties / brandPartner
      Added value: +{
      +  "description": "sponsoring brand's channel id (UC…) or @handle — gives that brand access to run the video as a partnership ad; \"\" unlinks (update only)",
      +  "type": "string"
      +}
    • addedInput schema / properties / defaultAudioLanguage
      Added value: +{
      +  "description": "spoken language, e.g. \"es\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / defaultLanguage
      Added value: +{
      +  "description": "language of title/description, e.g. \"en\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / embeddable
      Added value: +{
      +  "description": "true = allow embedding on other sites",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / license
      Added value: +{
      +  "description": "YouTube licence: youtube (standard) or creativeCommon",
      +  "enum": [
      +    "youtube",
      +    "creativeCommon"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / localizations
      Added value: +{
      +  "additionalProperties": {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "description": "translated title/description per language, e.g. {\"es\":{\"title\":\"…\"}}; needs defaultLanguage",
      +  "propertyNames": {
      +    "type": "string"
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / paidProductPlacement
      Added value: +{
      +  "description": "true = contains PAID product placement (sponsored) — YouTube shows the disclosure; legally required for sponsored content",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / publicStatsViewable
      Added value: +{
      +  "description": "true = show public view and like counts",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / recordingDate
      Added value: +{
      +  "description": "YYYY-MM-DD",
      +  "type": "string"
      +}
  5. Changed2 schema fields changedv0.1.374
    • changedInput schema / properties / account / description
      Previous value: -"WHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the brand has more than one youtube account connected (several and none named is refused by name, never guessed); omit when there is one."New value: +"WHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the profile has more than one youtube account connected (several and none named is refused by name, never guessed); omit when there is one."
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."New value: +"WHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted."
  6. Changed5 schema fields changedv0.1.320
    • changedInput schema / properties / brand / description
      Previous value: -"WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against."New value: +"WHICH BRAND this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no brand, or two, is REFUSED and nothing is posted."
    • addedInput schema / properties / coverAtMs
      Added value: +{
      +  "description": "THE VIDEO COVER (the custom thumbnail), as ONE frame: milliseconds from the start (7000 = the frame at 7s). That frame is cut from the upload and set with thumbnails.set. thumbnailUrl wins; this beats platformCover.",
      +  "type": "number"
      +}
    • changedInput schema / properties / hook / description
      Previous value: -"WHAT ANGLE THIS POST IS BUILT ON — the single most valuable field here, and the only moment it can ever be recorded. post_performance groups on it to answer \"which hooks work\", and it needs 5 posts sharing ONE hook before it will call anything a winner, so REUSE THE SAME WORDING across a campaign instead of rephrasing it every time. Best of all, pass a hook id from list_hooks (e.g. \"direct_callout\", \"mid_problem\", \"before_after\") — those fold onto a stable key however they are spelled, so a whole brand accumulates evidence on one row. Your own wording is fine too; it just only groups when you repeat it exactly. Omitting it means this post can never vote on which hook works."New value: +"WHAT ANGLE this post is built on, recorded only at publish time. post_performance ranks hooks on it (a winner needs 5 posts sharing ONE hook), so pass a list_hooks id (e.g. \"direct_callout\", \"before_after\") or reuse your own wording EXACTLY across a campaign. Omit it and this post never votes on which hook works."
    • changedInput schema / properties / privacy / description
      Previous value: -"default unlisted (anyone-with-link, ad-ready); public = live + searchable on the channel (confirm first); private = eyes-only (cannot run as an ad)"New value: +"default public (live + searchable on the channel); unlisted = link-only (the ad-ready setting, or to add YouTube music in Studio first — only when the user asks); private = eyes-only (cannot run as an ad)"
    • changedInput schema / properties / subject / description
      Previous value: -"WHAT THIS POST IS ABOUT — the product, feature, offer or theme (e.g. \"winter coat\", \"free trial\", \"founder story\"). The second grouping axis in post_performance. Same rule as hook: reuse the exact wording so posts about one subject land in one group."New value: +"WHAT THIS POST IS ABOUT — product, feature, offer or theme (e.g. \"winter coat\", \"free trial\"). post_performance's second grouping axis: reuse the exact wording, as with hook."
  7. Changed2 schema fields changedv0.1.281
    • addedInput schema / properties / ideaId
      Added value: +{
      +  "description": "short id of the content-plan idea this post came from",
      +  "type": "string"
      +}
    • addedInput schema / properties / recipe
      Added value: +{
      +  "description": "the post's FORMAT id, e.g. \"slideshow\" or \"imessage_chat\" — post_performance groups by it, so reuse one id per format",
      +  "type": "string"
      +}
  8. Changed1 schema field changedv0.1.256
    • addedInput schema / properties / platformCover
      Added value: +{
      +  "description": "VIDEO COVER. Omit it (the default) and Hermoso sets the video’s best frame — the same frame as its Library thumbnail — as the cover (YouTube custom thumbnail; the same as thumbnailUrl:\"auto\" when true). true = send no cover and let the platform pick (usually the first frame). A cover you pass yourself always wins.",
      +  "type": "boolean"
      +}
  9. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / brand
      Added value: +{
      +  "description": "WHICH BRAND this post belongs to — the id or exact name from list_brands (a workspace shared with you: its profile id). Use it whenever the account has more than one brand and you are not certain which one this connection is pinned to: it beats the pin for THIS CALL ONLY and changes nothing about the connection. A name that matches no brand, or two brands, is REFUSED and nothing is posted — never resolved to the pin, which is the account you were guarding against.",
      +  "type": "string"
      +}
  10. Changed1 schema field changedv0.1.243
    • addedInput schema / properties / thumbnailUrl
      Added value: +{
      +  "description": "the custom thumbnail: a Hermoso-hosted image (make_thumbnail, or upload_file for the user’s own). Omit it and a representative frame of the video is set, free; \"auto\" keeps YouTube’s pick. Custom thumbnails need a verified channel.",
      +  "type": "string"
      +}
  11. Changed3 schema fields changedv0.1.209
    • addedInput schema / properties / aiGenerated
      Added value: +{
      +  "description": "YouTube’s “altered or synthetic content” declaration (containsSyntheticMedia). OMIT IT and Hermoso decides from provenance: a Hermoso render is declared, a video the user uploaded through upload_file or from an external URL is NOT — real footage must not carry the label. true/false overrides.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / description / description
      Previous value: -"video description (≤5000 chars)"New value: +"REQUIRED in practice — what the video shows, a line about the brand, a link and a few #hashtags (≤5000 chars); YouTube search, suggested videos and the Shorts feed rank on it, so an upload with no description (and no caption) is refused"
    • changedInput schema / properties / title / description
      Previous value: -"video title (≤100 chars)"New value: +"REQUIRED in practice — the headline every search result and the Shorts feed shows (≤100 chars); an upload with no title is refused"
  12. Changed1 schema field changedv0.1.189
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "WHICH connected account of this channel to post as — its @handle or id from list_connector_accounts. Needed only when the brand has more than one youtube account connected (several and none named is refused by name, never guessed); omit when there is one.",
      +  "type": "string"
      +}
  13. Addedv0.1.161

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare a destructive, open-world, non-idempotent write; the description goes well beyond that with the crucial disclosure that publishing is PUBLIC BY DEFAULT, that subscribers are notified, and that a wrong notification cannot be undone. It also discloses the scheduling constraint (publishAt forces private) and that refusal happens rather than partial success. It stops short of describing the response payload or what a failed/partial publish leaves behind.

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

Conciseness4/5

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

The paragraph is dense but front-loaded: trigger, cost, default behavior, then exceptions. Capitalized emphasis on the destructive default makes the important part scannable. It is somewhat longer than needed because privacy and scheduling rules restate constraints also present in the schema.

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?

For a 30-parameter publishing tool with no output schema, the description covers the decisions that matter: default visibility, notification implications, ad eligibility, mandatory-in-practice title/description, account/profile disambiguation, and where to find full rules. An agent can call this safely without opening additional documentation.

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?

Schema coverage is 100%, so the baseline is 3; the description still earns credit for cross-parameter behavior, notably the privacy/notify/scheduling coupling and the ad-vs-unlisted rule, which an agent must understand as a policy rather than a field default. Most individual field meanings, however, are already carried by the unusually rich schema descriptions, so the gain is incremental.

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 ('Publish a finished video to the brand's connected YouTube channel') and scopes it to a channel rather than a search or file operation. It also implicitly distinguishes itself from upload_file by naming that sibling as the path for local files.

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

Usage Guidelines5/5

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

Opens with the triggering condition ('when the user wants to upload a video or Short to YouTube') and gives explicit routing to upload_file for local/external files. It adds conditional rules for privacy (ad → unlisted, private cannot be an ad, never choose unlisted for music unprompted) and a prerequisite (connected YouTube channel), plus a pointer to get_instructions for full rules.

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