Skip to main content
Glama

vibedeploy

by be.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 hosted on vibedeploy.be are skipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesSite name (subdomain) whose external images should be downloaded and rehosted locally.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
siteIdYes
failuresYesExternal image URLs that could not be rehosted (left untouched in the HTML).
request_idNoServer-assigned request correlation id. Quote it when contacting support.
bytesHostedYes
imagesHostedYesNumber of external images downloaded and stored on the site.
htmlFilesUpdatedYesNumber of HTML files whose img references were rewritten to local paths.

TDQS

A4.5/5.0
Behavior5/5

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

Adds significant detail beyond annotations: SSRF-guarded, size/count/time capped, atomic patch mode, and skipping vibedeploy.be images. No contradiction with annotations (destructiveHint=true, readOnlyHint=false, etc.).

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 sentences: first states action, second gives timing/usage, third adds behavioral details. Every sentence is meaningful. No unnecessary words.

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?

Given a single required parameter, clear usage instructions, behavioral safeguards, and the presence of an output schema (complete coverage of return values), the description covers all essential aspects.

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 ('name') with 100% schema coverage. The description does not add new meaning beyond the schema's description; it implies the site's HTML is scanned. Baseline score of 3 is appropriate.

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 uses a specific verb ('Download and store') and resource ('external images for a site') and clearly states the outcome: rewriting HTML references. It distinguishes itself from sibling tools (which include deploy, file operations, etc.) by focusing on image rehosting post-deployment.

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?

Explicitly states when to call: 'once AFTER deploying a site rebuilt with the Website Converter.' It also notes that images already hosted on vibedeploy.be are skipped, implying idempotent use. Does not explicitly state when not to use, but the context is clear.

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

All vibedeploy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from deployment and file management to domain configuration and analytics. Even similar-sounding tools like add_files and add_file_chunk are well-differentiated by context and use case.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_custom_domain, list_sites, delete_source_file). The naming is predictable and easy to understand.

Tool Count4/5

39 tools is higher than the typical 3-15 range, but each tool serves a necessary function for a comprehensive deployment platform. The count is justified by the broad feature set, though slightly heavy.

Completeness5/5

The tool set covers the full lifecycle of site deployment, management, backup, custom domains, form handling, analytics, and source editing. There are no obvious gaps for the intended functionality.

Resources