UiChemy AI Website Creator

uichemy_publish_site

Destructive

Put a project ONLINE as a real WordPress site at https://.uichemysites.com, hosted by UiChemy: the pages are exported and imported into WordPress with the UiChemy plugin. This is PUBLIC: anyone with the link can see it, so only call it when the user asks to publish, go live, or put the site online, and tell them the address. One site per project; calling it again for a published project UPDATES that same site (same address, pages replaced with the current design). A new site is a Temporary site: online for 24 hours, then offline until the user turns it on again or makes it permanent (Sandbox) in UiChemy > Published Sites. Each plan allows a number of Temporary and Sandbox sites; unpublishing or going offline frees one. Only generated pages are published. PAGE BUILDER: before a FIRST publish, ask the user whether the WordPress pages should be built with Elementor (recommended) or Gutenberg (the WordPress block editor), unless they already said, and pass it as builder. If they don't know or say "you choose", use Elementor without asking again. A site keeps that builder: on an update leave builder out; to switch builder the site has to be unpublished first, unless its first publish failed (then a retry may pass the other builder). Publishing takes a few minutes: this returns at once with the address; then call uichemy_publish_status (it waits for the result) until it says live or FAILED, and only then tell the user the site is live or that it failed. WordPress only: for an Astro site use uichemy_export_astro (download) or uichemy_deploy_to_cloudflare (the user's own Cloudflare). To open the site's WordPress admin afterwards, use uichemy_open_site_admin (the user has no password for it).

Input Schema

Name	Required	Description
`pages`	No	Page names to publish. Omit for every generated page.
`address`	No	Only for a FIRST publish: the subdomain, e.g. "bloom-bakery" for bloom-bakery.uichemysites.com. Lowercase letters, numbers and hyphens. Omit to derive it from the project name. Ignored on an update.
`builder`	No	Only for a FIRST publish: the page builder the user chose, elementor or gutenberg. Ask them first. Omitted on a first publish = elementor. Leave out on an update (the site keeps its builder).
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / builder

Added value: +{
+  "description": "Only for a FIRST publish: the page builder the user chose, elementor or gutenberg. Ask them first. Omitted on a first publish = elementor. Leave out on an update (the site keeps its builder).",
+  "enum": [
+    "elementor",
+    "gutenberg"
+  ],
+  "type": "string"
+}

First observedOct 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations flag destructive/openWorld/non-readonly, and the description adds substantial context beyond them: public visibility, one-site-per-project update semantics that replace pages, 24-hour Temporary lifetime, plan limits, builder retention, and the requirement to switch builders only after unpublishing. No contradiction with destructiveHint=true — the page-replacement note supports it.

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?

Front-loaded with the core action and destination, then the public/visibility caveat, then the update/plan/builder mechanics. It is long, but nearly every sentence carries operational information the agent needs; some budget/temporary-site detail could be trimmed without loss.

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?

There is no output schema, yet the description explains the return behavior (returns immediately with the address) and the required status-polling handshake before reporting success. For a destructive, asynchronous, public-facing operation, the description covers everything needed to call it correctly.

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?

At 75% schema coverage the schema already documents each parameter, but the description adds real operational meaning for `builder` (ask the user first, default Elementor, omit on update, switching requires unpublish or a failed first publish) and reinforces that `address` applies only to first publish. `pages` is left to the schema.

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?

Starts with a concrete verb+resource+destination: putting a project online as a real WordPress site at a named domain, with the mechanism (export/import via the UiChemy plugin) stated. It also explicitly distinguishes itself from the sibling alternatives (uichemy_export_astro, uichemy_deploy_to_cloudflare).

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?

Gives explicit call conditions ('only call it when the user asks to publish, go live, or put the site online'), names the sibling alternatives for non-WordPress targets, and prescribes the follow-up loop with uichemy_publish_status. It also distinguishes first publish vs update behavior, which drives the agent's parameter choices.

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

All UiChemy AI Website Creator tools Inspect

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

Need Help?