Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Import images into a site's media library

import_images_from_url
Idempotent

Copy images the user picked (from find_images_at_url) into the site's media library as permanent files. Importing the same image again reuses it. They are NOT placed on a page — place one with apply_hero_pattern, apply_image_replacements or refine_site.

Input Schema

NameRequiredDescriptionDefault
imagesYesThe images the user picked, from find_images_at_url.
site_idYesThe site to act on
user_goalNoOptional: 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.

  1. Changed1 schema field changed
    • 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"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true, so the baseline is covered. The description still adds value by explaining what idempotency means concretely ('Importing the same image again reuses it') and that files become permanent library assets, though it omits failure behavior for unreachable URLs and any size/permission constraints.

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?

Three short sentences, none wasted: effect first, dedupe behavior second, placement exclusion and handoff third. Front-loaded and easy to scan.

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?

With no output schema, the description could ideally say what comes back (e.g. media IDs for later use), which matters since the follow-up tools presumably need those references. Otherwise it covers effect, dedupe, and scope fully for a simple import tool.

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 all three parameters are documented in the schema, making 3 the baseline. The description adds only that the images array is 'the user picked' from find_images_at_url, with no extra detail on alt text, source_page_url, or user_goal semantics.

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 ('Copy images ... into the site's media library as permanent files') and names the upstream sibling find_images_at_url as the source. It is clearly distinguishable from placement tools like apply_image_replacements or apply_hero_pattern.

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?

Explicitly scopes usage: images the user picked from find_images_at_url, and it states the tool does NOT place images on a page, routing the agent to apply_hero_pattern, apply_image_replacements or refine_site for that. Both the when and the when-not-with-alternatives are stated.

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

All Mondovo 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