Skip to main content
Glama

Import a project from a ZIP file

import_zip
Destructive

Imports a multi-file website from a ZIP archive into an existing site. index.html (or the only HTML file in the root) becomes the page and is published; other HTML pages go to the site root with clean addresses (about.html at /about); all other files go to assets/ with their folders kept (assets/css/style.css, assets/img/logo.png). Relative paths are rewritten automatically. Send the archive as zip_base64 (base64 string) or zip_url (public http/https link, e.g. a GitHub archive URL). Limits: ZIP up to 20 MB, 300 files, 10 MB per file, the account storage limit. Allowed files: html, css, js, json, images (jpg, png, gif, svg, webp, avif, ico), fonts (woff, woff2, ttf, otf), txt, xml, pdf. Use dry_run=true first to see what would happen. The previous index.html is kept in version history (restore_version).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "import_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id or name, e.g. "my-portfolio" or "my-portfolio.hostilo.page" (from list_sites).
dry_runNoOnly check the archive and report what would be imported; nothing is changed.
zip_urlNoPublic http/https URL of the ZIP file (max 20 MB, up to 3 redirects). Use this or zip_base64.
zip_base64NoThe ZIP file encoded as base64 (max 20 MB decoded). Use this or zip_url.
clear_assetsNoDelete all current files in assets/ before importing.
expected_versionNoOptional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site / description
      Previous value: -"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.app\" (from list_sites)."New value: +"Site id or name, e.g. \"my-portfolio\" or \"my-portfolio.hostilo.page\" (from list_sites)."
  2. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
      +  "description": "Optional: the version from get_site. If the site was saved by someone else since then, nothing is published and you get a version_conflict error (get the site again and merge).",
      +  "type": "string"
      +}
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds substantial context beyond them: exact file placement rules, automatic relative-path rewriting, size/file/type limits, the fact that the previous index.html is preserved in version history, and the expected_version conflict behavior.

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?

Information is front-loaded: purpose first, then the mapping rules, then input method, then limits and safe-usage advice. It is dense but nearly every sentence carries operational detail; the limit list is the only slightly listy passage.

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 destructive, open-world mutation with no output schema, the description covers the consequence of the call, acceptable inputs, hard limits, concurrency handling, and recovery. Nothing an agent needs in order to invoke it safely is missing.

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 100%, so baseline is 3; the description still adds value by giving a concrete zip_url example (GitHub archive), restating the size ceilings, and framing dry_run as a mandatory first step rather than an optional flag.

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 (imports a multi-file website from a ZIP archive into an existing site) and then spells out the resulting filesystem layout, which makes the tool's effect unambiguous and distinguishable from publish_files or update_site.

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 clear operating guidance: 'Use dry_run=true first to see what would happen' and the choice between zip_base64 and zip_url, plus the restore_version escape hatch. It stops short of explicitly naming when to prefer this over the sibling publish_files tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.