AIfra — temporary static previews

create_preview

Prepare a new temporary static preview. Supply exactly one of small files or ZIP archive_base64. No backend/build. Requires explicit consent; returns an approval link, not a published URL. User must confirm in their browser.

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": {
      "accept_terms": "<accept_terms>"
    },
    "name": "create_preview"
  }
}

Input Schema

Name	Required	Description
`files`	No	One input choice: 1-500 already-built static files, at most 1 MiB decoded in total. Include index.html at the root and all needed assets. Do not also send archive_base64 or archive. For larger output use a ZIP.
`accept_terms`	Yes	Set true only after the user explicitly agrees to the current terms and public temporary preview limits. Not inferred from a request to generate a site. Preparation is not publication; the user must also personally confirm the approval URL in their browser within 2 hours.
`archive_base64`	No	One input choice: actual ZIP bytes encoded as canonical standard base64, without data: prefix. At most 50 MiB (52,428,800 bytes) of decoded ZIP and 50 MiB extracted content; at most 25 MiB per file. index.html at root. No nested archives or server code. Do not also send files or archive.

Output Schema

Name	Required	Description
`status`	Yes
`message`	Yes	Next user action; preparation has not published or deleted anything.
`preview_id`	Yes	AIfra preview identifier; never a management key.
`approval_url`	Yes	Return to the user to open personally. This is not the published preview URL. Never approve it on their behalf.
`operation_id`	Yes	Prepared operation identifier.
`approval_expires_at`	Yes	Preparation expires after 2 hours. The 48-hour preview starts only after confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 12, 2026

addedInput schema / properties / accept_terms / description

Added value: +"Set true only after the user explicitly agrees to the current terms and public temporary preview limits. Not inferred from a request to generate a site. Preparation is not publication; the user must also personally confirm the approval URL in their browser within 2 hours."

addedInput schema / properties / archive_base64 / description

Added value: +"One input choice: actual ZIP bytes encoded as canonical standard base64, without data: prefix. At most 50 MiB (52,428,800 bytes) of decoded ZIP and 50 MiB extracted content; at most 25 MiB per file. index.html at root. No nested archives or server code. Do not also send files or archive."

addedInput schema / properties / files / description

Added value: +"One input choice: 1-500 already-built static files, at most 1 MiB decoded in total. Include index.html at the root and all needed assets. Do not also send archive_base64 or archive. For larger output use a ZIP."

addedInput schema / properties / files / items / properties / content / description

Added value: +"Actual file contents, not a filename, local path or download URL. Use UTF-8 text for HTML/CSS/JS and canonical base64 for binary assets. All files together must decode to at most 1 MiB (1,048,576 bytes). No secrets, personal/payment data or forms."

addedInput schema / properties / files / items / properties / encoding / description

Added value: +"Defaults to utf8. Set base64 for binary content; standard padded base64 only, without a data: prefix, whitespace or URL-safe alphabet. The decoded bytes count toward the shared 1 MiB limit."

addedInput schema / properties / files / items / properties / path / description

Added value: +"Relative POSIX path inside the ready static output, e.g. index.html or assets/app.js. index.html must be at the root. No absolute paths, traversal, symlinks, archives or executable/server files."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "approval_expires_at": {
+      "description": "Preparation expires after 2 hours. The 48-hour preview starts only after confirmation.",
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+      "type": "string"
+    },
+    "approval_url": {
+      "description": "Return to the user to open personally. This is not the published preview URL. Never approve it on their behalf.",
+      "format": "uri",
+      "type": "string"
+    },
+    "message": {
+      "description": "Next user action; preparation has not published or deleted anything.",
+      "type": "string"
+    },
+    "operation_id": {
+      "description": "Prepared operation identifier.",
+      "pattern": "^rop_[A-Za-z0-9_-]{43}$",
+      "type": "string"
+    },
+    "preview_id": {
+      "description": "AIfra preview identifier; never a management key.",
+      "pattern": "^pv_[A-Za-z0-9_-]{24}$",
+      "type": "string"
+    },
+    "status": {
+      "const": "pending",
+      "type": "string"
+    }
+  },
+  "required": [
+    "operation_id",
+    "status",
+    "preview_id",
+    "approval_url",
+    "approval_expires_at",
+    "message"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / archive

Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "download_url": {
-      "maxLength": 8192,
-      "type": "string"
-    },
-    "file_id": {
-      "maxLength": 256,
-      "minLength": 1,
-      "type": "string"
-    },
-    "file_name": {
-      "maxLength": 240,
-      "type": "string"
-    },
-    "mime_type": {
-      "maxLength": 100,
-      "type": "string"
-    }
-  },
-  "required": [
-    "download_url",
-    "file_id"
-  ],
-  "type": "object"
-}

First observedSep 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only cover the safety profile (non-readonly, open-world, non-idempotent, non-destructive). The description adds materially new behavior: an explicit consent gate, that preparation is not publication, that the return is an approval link rather than a live URL, and that the user must personally confirm in a browser, which are exactly the workflow facts an agent needs.

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?

Four short sentences, front-loaded with purpose and then the input constraint, consent requirement and return semantics in descending order of importance. No filler and every sentence carries a distinct fact.

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?

An output schema exists so return structure need not be explained, and the description covers consent, input exclusivity and the approval-link nature of the result. It omits the confirmation time window (2 hours) and size limits, though those are present in the schema, so it is nearly complete for this complexity level.

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 the schema already documents paths, encodings, size limits and the mutual-exclusion rule in detail. The description's 'exactly one of small files or ZIP archive_base64' reinforces the cross-parameter constraint but adds nothing the schema lacks, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Prepare a new temporary static preview') with scope qualifiers ('No backend/build') and clarifies that the output is an approval link, not a published URL. It does not name or explicitly contrast with any sibling (e.g., update_preview, get_deploy_instructions), so the sibling differentiation is inferred rather than stated.

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 a real selection rule ('supply exactly one of small files or ZIP archive_base64') and an implicit when-not ('No backend/build' rules out dynamic sites), plus the precondition of explicit consent. It never states when to choose this over update_preview or how it fits the broader preview lifecycle, so exclusions/alternatives are incomplete.

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

All AIfra — temporary static previews tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?