Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Upload a local file -> durable public URL

upload_file

Upload any user file (image, video, audio, PDF, up to 150MB) to Hermoso to get a durable public URL accepted by every publish, schedule, and ad-build tool.

Instructions

Persist an ARBITRARY user file (image, video, audio, PDF or document, up to 150MB) into Hermoso and get back a durable public URL that EVERY publish, schedule and ad-build tool accepts — post_to_meta / post_to_linkedin / post_to_linkedin_page / post_to_youtube / post_to_tiktok / post_to_pinterest / post_to_x / post_to_google_business / schedule_post / upload_meta_asset / upload_google_ads_asset / create_meta_ad / create_linkedin_ads_creative / set_youtube_thumbnail / save_to_drive / save_to_onedrive. THIS IS THE BRING-YOUR-OWN-CREATIVE PATH: it is for files that have NOTHING to do with a Hermoso render (media on the user's desktop, an agency's finished ad, a photo they shot), and it means you can publish, schedule and run ads through Hermoso without generating anything here. Provide exactly ONE source — passing two is an error, never a silent preference: url (ANY public http(s) link — Hermoso fetches it server-side, so nothing crosses this connection and there is no practical size limit; THIS IS THE ONE THAT ALWAYS WORKS, including on the hosted connector), path (a local file, ONLY when Hermoso runs on the user's own machine over stdio/CLI; the hosted connector cannot see their disk), or dataUri (a base64 data: URI — keep it under ~15MB, since the bytes travel over this connection). If the file is already at a public https URL, the Meta, Reddit and ChatGPT-Ads tools take it directly and re-host it safely — but LinkedIn (posts and ad creatives), Pinterest, the YouTube thumbnail and upload_google_ads_asset upload the BYTES themselves and therefore refuse an external host, so run it through here first and pass the URL this returns. When in doubt, use this: its URL works everywhere. (Calling the underlying HTTP route directly? POST /api/upload takes the file's RAW BYTES as the request body with its own content-type — NOT multipart/form-data — or ?url= with no body.) Returns {url, kind, bytes}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoa PUBLIC http(s) URL Hermoso fetches server-side (private/internal addresses are refused, and every redirect hop is re-checked). Works on every surface including the hosted connector, and the bytes never cross this connection — prefer this whenever the file is reachable on the web.
nameNooriginal file name — helps pick the right extension
pathNolocal filesystem path (stdio/CLI only — refused on the hosted connector)
dataUriNobase64 data: URI of the file bytes (data:<mime>;base64,<…>) — bytes travel over this connection, so keep it small
getUploadUrlNoASK FOR A ONE-TIME UPLOAD URL instead of uploading now — use this whenever the file is on the user’s machine and you can run a shell or an HTTP request. Returns a uploadUrl you PUT the raw bytes to (any HTTP client), which answers with the durable Hermoso url. It beats `dataUri` for anything but a small image: a data: URI spends the whole file as tokens in this conversation. One file per url, and it expires.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.251
    • addedInput schema / properties / getUploadUrl
      Added value: +{
+  "description": "ASK FOR A ONE-TIME UPLOAD URL instead of uploading now — use this whenever the file is on the user’s machine and you can run a shell or an HTTP request. Returns a uploadUrl you PUT the raw bytes to (any HTTP client), which answers with the durable Hermoso url. It beats `dataUri` for anything but a small image: a data: URI spends the whole file as tokens in this conversation. One file per url, and it expires.",
+  "type": "boolean"
+}
  2. Changed3 schema fields changedv0.1.161
    • changedInput schema / properties / dataUri / description
      Previous value: -"base64 data: URI of the file bytes (data:<mime>;base64,<…>)"New value: +"base64 data: URI of the file bytes (data:<mime>;base64,<…>) — bytes travel over this connection, so keep it small"
    • addedInput schema / properties / url
      Added value: +{
+  "description": "a PUBLIC http(s) URL Hermoso fetches server-side (private/internal addresses are refused, and every redirect hop is re-checked). Works on every surface including the hosted connector, and the bytes never cross this connection — prefer this whenever the file is reachable on the web.",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "bytes": {
-      "type": "number"
-    },
-    "kind": {
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Addedv0.1.15

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only signal write, non-idempotent, non-destructive. The description adds far more: the 150MB limit, the fact that passing two sources is an explicit error, the server-side fetch vs local disk vs connection-traveling bytes distinctions, the 'always works' reliability cue for url, and the return shape {url, kind, bytes}. It also documents the direct HTTP route behavior. No contradiction with annotations.

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?

The description is long but every sentence carries distinct operational information. It is front-loaded with the core purpose, then systematically addresses source selection, per-channel requirements, and finally the HTTP route and return format. There is no redundant filler; the length is justified by the tool's complexity.

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?

With 5 parameters, no output schema, and a potentially confusing role among many sibling tools, the description covers all bases: when to use, which parameter to pick, size constraints, connector-specific behavior, and return format. An agent has everything needed to call this tool correctly without additional lookups.

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 descriptions already cover all 5 parameters (100% coverage), so the baseline is 3. The description adds extra semantics beyond the schema: it clarifies that 'two is an error', names url as the always-works option, explains the stdio/CLI restriction for path, and positions getUploadUrl as the preferred path for local files over dataUri. This pushes it above baseline.

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 clearly states a specific verb ('Persist... get back a durable public URL') and resource ('ARBITRARY user file') while distinguishing itself from render-related workflows: 'THIS IS THE BRING-YOUR-OWN-CREATIVE PATH'. It explicitly lists the sibling tools that accept its output, making its role unmistakable.

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?

Provides explicit when-to-use and when-not-to-use guidance: it's for files unrelated to Hermoso renders, and it names the alternative paths (post_to_meta etc. take the URL directly, while LinkedIn, Pinterest, YouTube thumbnail, and google ads asset require uploading through here first). It even says 'When in doubt, use this', leaving nothing to inference.

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