UiChemy AI Website Creator

uichemy_deploy_to_cloudflare

Destructive

Put a project ONLINE on the user's OWN Cloudflare account (a Cloudflare Worker at https://..workers.dev), built as a static site from the same pages as the Astro export. This is PUBLIC: only call it when the user asks to deploy or publish to Cloudflare, and tell them the address. The first time, the account is not connected yet: this returns a link the user must open to approve UiChemy on Cloudflare; after they have, call this again. If their Cloudflare login has several accounts, this lists them: ask which one and pass its accountId. Calling it again for a deployed project UPDATES the same site (its pages are replaced with the current design). Every deploy is a numbered version; uichemy_site_versions lists them and uichemy_restore_site_version puts an earlier one back online. Only generated pages are deployed.

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": {
      "projectId": "<projectId>"
    },
    "name": "uichemy_deploy_to_cloudflare"
  }
}

Input Schema

Name	Required	Description
`pages`	No	Page names to deploy. Omit for every generated page.
`accountId`	No	Cloudflare account id, only when this tool listed several. Omit otherwise.
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 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 and open-world, but the description adds crucial context the annotations cannot convey: the site becomes PUBLIC, re-deploying replaces existing pages with the current design, every deploy is a numbered version, and only generated pages ship. That's exactly the extra behavioral detail an agent needs before a destructive public action.

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 outcome and the public/deploy gate, then the branching auth flow. Dense and almost every clause earns its place, though the parenthesis-heavy sentence about the Worker URL makes it slightly harder to scan.

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?

No output schema exists, so the description explains returns itself: a link to approve UiChemy on first run, or a list of accounts if several exist. Combined with the update/version semantics, an agent has everything needed to call this 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?

Schema coverage is 67%, and the description compensates well: it explains when accountId is needed (only after the tool listed several accounts) and that only generated pages are deployed, reinforcing the pages parameter. projectId is left to the schema, which is a minor gap but obvious from context.

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 concrete verb and resource: puts a project online as a Cloudflare Worker at a named URL, built as a static site from the same pages as the Astro export. This clearly separates it from siblings like export_astro, publish_site, and publish_emdash.

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?

Explicitly gates usage: 'only call it when the user asks to deploy or publish to Cloudflare' and 'tell them the address.' It also covers the first-run OAuth branch, the multi-account branch, and points at uichemy_site_versions / uichemy_restore_site_version for version management.

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?