VibeDeploy

Rehost a site's external images locally

rehost_images

DestructiveIdempotent

Download the external images a site references (e.g. from the old site it was rebuilt from), store them on this VibeDeploy site under assets/img/, and rewrite the HTML references to local paths so the site no longer depends on the original. Call this once AFTER deploying a site rebuilt with the Website Converter. Auto-detects the external image URLs from the site's own HTML; downloads are SSRF-guarded, size/count/time capped, and applied atomically (patch mode). Images already on a VibeDeploy platform domain are skipped.

Input Schema

Name	Required	Description	Default
`name`	Yes	Site name as shown by list_sites, whose external images are downloaded and stored on the site.

Output Schema

Name	Required	Description
`name`	Yes
`siteId`	Yes
`failures`	Yes	External image URLs that could not be rehosted (left untouched in the HTML).
`bytesHosted`	Yes
`imagesHosted`	Yes	Number of external images downloaded and stored on the site.
`htmlFilesUpdated`	Yes	Number of HTML files whose img references were rewritten to local paths.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / name / description

Previous value: -"Site name (subdomain) whose external images should be downloaded and rehosted locally."New value: +"Site name as shown by list_sites, whose external images are downloaded and stored on the site."

Changed1 schema field changedSep 6, 2026

removedOutput schema / properties / request_id

Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}

First observedJun 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations declare the safety profile (destructive, idempotent, open world), and the description adds genuinely new operational detail: SSRF guarding, size/count/time caps, atomic patch-mode application, and that platform-domain images are skipped. This is substantially more than the annotations provide.

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 but front-loaded: the core action comes first, then usage timing, then behavioral caveats. Every clause carries information, though the second and third sentences are long and could be tightened.

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?

An output schema exists, so return values need no explanation, and the description covers the prerequisites, side effects, and safety limits an agent needs before invoking a destructive-but-idempotent mutation.

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?

Only one parameter and schema description coverage is 100%, so the schema already defines 'name' fully. The description reinforces that images are auto-detected from the site's own HTML (i.e. no URL list is passed), which is mildly useful, but adds no syntax or format information.

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 chain (download, store, rewrite) with a concrete resource and destination path (assets/img/), and distinguishes itself from deployment siblings like deploy_site by describing a post-deploy normalization step. An agent can identify exactly what this does without opening the schema.

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

Usage Guidelines4/5

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

Gives explicit timing and precondition: 'Call this once AFTER deploying a site rebuilt with the Website Converter.' That is clear when-to-use guidance, though it names no alternative tool or when-not-to-call condition (e.g. a site with no external images).

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

All VibeDeploy tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.