Mondovo

Upload a media asset to a site

upload_asset

Store an image or video permanently in a site's media library and get back a stable, non-expiring URL you can use in the design. (For Creative Studio — visuals and films — use upload_brand_asset instead: it reads a brand's Library, not a site's.) Give a site_id and an HTTPS url pointing at the media (a generated image/video, a stock URL, or a temporary/expiring signed URL) — Mondovo downloads it, stores it permanently, and returns the permanent url. Use this when you have media at a link that might expire, or that you generated elsewhere, and you want it to live with the site. Supported: images (JPG, PNG, WebP, GIF) and video (MP4, WebM, MOV, up to 80 MB). Returns the permanent url plus an asset_id; reference the url in a subsequent refine_site instruction to place the asset.

Input Schema

Name	Required	Description
`url`	Yes	HTTPS URL of the image or video to store permanently
`site_id`	Yes	The site to add the asset to
`alt_text`	No
`filename`	No
`user_goal`	No	Optional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / user_goal

Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds substantial behavior beyond them: Mondovo downloads the remote media, persists it, enforces supported formats and an 80 MB cap, and returns both a permanent url and asset_id. It does not address repeat-upload behavior despite idempotentHint=false, leaving an agent unsure whether re-uploading the same URL duplicates assets.

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?

Dense and front-loaded — purpose, then the sibling exclusion, then the mechanics, then return values. The parenthetical about Creative Studio interrupts the opening sentence and slightly hurts flow, but almost every clause carries information an agent needs.

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 single-step upload tool with no output schema, the description supplies everything needed: input constraints (formats, 80 MB, HTTPS), transformation behavior (download-and-rehost), and both return fields (url, asset_id). The only missing element, duplicate-upload semantics, is minor given the low-risk non-destructive annotation.

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 60%, and the description compensates well on the two required params: it clarifies that url may be a generated image/video, a stock URL, or a temporary/expiring signed URL, and must be HTTPS — meaning the tool resolves expiring links rather than rejecting them. However, alt_text and filename have no description in the schema and are never mentioned, so those stay opaque.

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 first sentence gives a specific verb and resource ('Store an image or video permanently in a site's media library') plus the outcome (stable, non-expiring URL). It explicitly names the sibling it is not — upload_brand_asset — with the distinguishing reason (brand's Library vs. site's), so an agent can disambiguate without opening schemas.

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?

Explicit when-to-use is given ('when you have media at a link that might expire, or that you generated elsewhere'), along with an explicit alternative and the condition that selects it (Creative Studio visuals/films → upload_brand_asset). It also names the downstream step (reference the url in a refine_site instruction), which is real routing guidance.

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

All Mondovo tools Inspect

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

Need Help?