Skip to main content
Glama
hermoso-ai

Hermoso

Official

Upload a local file → durable public URL

upload_file

Upload any image, video, or document to get a durable public URL that works across all publishing, scheduling, and ad platforms.

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_reddit / 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
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide only basic hints (non-readonly, non-idempotent, non-destructive). The description goes far beyond: error semantics (two sources = error, never silent preference), server-side fetch behavior with private-address refusal and per-hop redirect re-checks, size limits, the fact that bytes never cross the connection for url, and the raw-bytes HTTP route alternative. This fully discloses operational traits an agent needs.

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 description is dense but well-ordered: purpose and the core 'bring-your-own-creative' concept are front-loaded, then source options with constraints, then tool-specific re-hosting guidance, then return format. Every sentence earns its place, though the raw HTTP route detail (~40 words) is aimed at a developer calling the API directly rather than an AI agent, which trims efficiency slightly. It would benefit from tighter formatting, but there is no filler.

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 4-parameter tool with no output schema and tricky multi-surface behavior, the description is complete: it specifies the return shape ({url, kind, bytes}), all size constraints, per-surface availability, the one-source rule, and the full list of accepting tools. Nothing an agent needs to invoke it correctly is missing, and the no-required-params ambiguity is resolved by the explicit 'exactly ONE source' instruction.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial meaning the schema does not convey: it explains that url always works because Hermoso fetches server-side (so no connection limit), that path is refused on the hosted connector, and that dataUri has a practical 15MB ceiling because bytes travel over the connection. It also clarifies the mutual exclusion of the three source params, which the schema does not state — crucial given no param is marked required.

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 states a specific verb ('persist'), a resource (arbitrary user file), a concrete output (durable public URL), and a size ceiling (150MB). It also sharply differentiates itself from siblings by naming the 'bring-your-own-creative path' for files unrelated to Hermoso renders, and it enumerates every tool that accepts the returned URL. An agent cannot confuse this with the many publish/schedule siblings.

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?

Extremely explicit guidance: when to use it (user-owned creatives, not Hermoso renders), the exact one-source rule with 'passing two is an error', per-parameter selection criteria (url always works incl. hosted connector, path only on stdio/CLI, dataUri under 15MB), and which downstream tools take external URLs directly vs which require re-hosting through this tool. The 'when in doubt, use this' directive removes any ambiguity.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server