Carryo Website Publisher

Publish a Live Website

website.publish

Publishes supplied HTML as a new public Carryo website for sharing a presentation, proposal, report, dashboard, invitation, portfolio, or landing page. Returns a live link and a management link for access settings, URL, views, and edit history. New Personal websites consume the account creation allowance. Personal is the default destination; workspaceId selects a user-chosen team. Supports an optional customSlug and hosted images. Pass attached images through imageFiles. For one attachment, assets needs only its relative website path; Carryo matches the attachment automatically. For multiple attachments, use fileIndex (0 for the first imageFiles entry). Do not invent file IDs or ask for a public URL when attachment upload is available. Known fileId references and fetchable HTTP(S) sourceUrl imports also work. Carryo imports and hosts its own copy. Base64 image bytes and data URLs are unsupported. Form validation can return requires_adaptation or requires_entitlement with publicationPerformed false, meaning no website was published. Supports HTML pages and their image assets, without general file storage or backend hosting.

Input Schema

TableJSON Schema

Name	Required	Description
`forms`	No	Optional definitions for JavaScript/React forms using window.CarryoForms.submit(key, values), which resolves on acceptance and rejects on failure. Stable keys and field names identify forms across edits. Static collection forms are inferred from data-carryo-form="key" and named controls without duplicate definitions; placeholder submit handlers can block collection. Local calculator/filter forms use data-carryo-local and do not collect responses. Existing external endpoints retain their destination. Visitor acknowledgement is disabled unless explicitly enabled.
`assets`	No	Optional image assets to add or replace. Each entry requires a relative website path. With one imageFiles attachment, path alone uses that attachment. Otherwise select exactly one source: fileIndex (zero-based imageFiles position), a known fileId, or a fetchable HTTP(S) sourceUrl. Never guess generated file IDs. Existing images are preserved when omitted; replacing an existing path does not use another slot. Base64 bytes and data URLs are unsupported.
`fileName`	Yes	Short internal file name, for example client-proposal.html, board-deck.html, report.html, or landing-page.html.
`expiresAt`	No	Optional ISO-8601 expiration timestamp
`customSlug`	No	Optional user-chosen URL ending using lowercase letters, numbers, and hyphens. An automatic URL is generated when omitted.
`imageFiles`	No	Optional image attachments supplied through the host's file upload support. The host supplies file_id and download_url. Map each attachment to a website path in assets: with one attachment, path alone is sufficient; with multiple attachments, use fileIndex. The assistant does not need to know generated file IDs or download URLs. Temporary URLs are import sources, not hosted image URLs. Clients without file input support can omit this field.
`htmlContent`	Yes	Complete HTML for the page, presentation, slide deck, proposal, report, landing page, dashboard, invitation, portfolio, or one-page website to publish.
`sharingMode`	Yes	Publishing mode for the Carryo page. Only public live links are supported here.
`workspaceId`	No	Optional exact workspaceId of the Carryo team explicitly selected by the user. The default destination is Personal when omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No
`forms`	No
`linkId`	No	Carryo page link identifier
`status`	No
`message`	No
`guidance`	No
`shareUrl`	No	Primary share URL
`expiresAt`	No	Optional ISO-8601 expiration timestamp
`manageUrl`	No	Carryo web-app URL for managing the link URL, password, views, and edit history
`customSlug`	No	Optional custom URL ending
`workspaceId`	No	Workspace that owns the link; omitted for Personal
`alternateShareUrls`	No	Alternate share URLs, when available
`currentVersionNumber`	No
`publicationPerformed`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 25, 2026

changedInput schema / properties / assets / description

Previous value: -"Optional image assets to add or replace. Each entry requires a relative HTML path and exactly one of fileId (matching imageFiles[].file_id) or sourceUrl (a fetchable HTTP(S) image URL). Existing images are preserved when omitted. The hosted-image allowance applies to the final website collection; replacing an existing path does not use another slot. Base64 bytes and data URLs are unsupported."New value: +"Optional image assets to add or replace. Each entry requires a relative website path. With one imageFiles attachment, path alone uses that attachment. Otherwise select exactly one source: fileIndex (zero-based imageFiles position), a known fileId, or a fetchable HTTP(S) sourceUrl. Never guess generated file IDs. Existing images are preserved when omitted; replacing an existing path does not use another slot. Base64 bytes and data URLs are unsupported."

changedInput schema / properties / assets / items / properties / fileId / description

Previous value: -"Attachment file_id matching a host-supplied imageFiles entry. Mutually exclusive with sourceUrl."New value: +"Known attachment file_id matching an imageFiles entry. Prefer fileIndex if the host-generated ID is not visible. Mutually exclusive with fileIndex and sourceUrl."

addedInput schema / properties / assets / items / properties / fileIndex

Added value: +{
+  "description": "Zero-based position in imageFiles: 0 selects its first attachment. Use this when the host generates file IDs during upload. May be omitted when imageFiles contains exactly one attachment. Mutually exclusive with fileId and sourceUrl.",
+  "maximum": 19,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / assets / items / properties / sourceUrl / description

Previous value: -"Fetchable HTTP(S) image URL for Carryo to import and host. Mutually exclusive with fileId. Data URLs and base64 bytes are unsupported."New value: +"Fetchable HTTP(S) image URL for Carryo to import and host. Mutually exclusive with fileId and fileIndex. Data URLs and base64 bytes are unsupported."

changedInput schema / properties / imageFiles / description

Previous value: -"Optional image attachments supplied by a compatible host, with file_id and download_url. Each attachment is mapped to a relative HTML path by an assets entry with the matching fileId. Temporary download URLs are import sources, not hosted image URLs. Clients without file input support can omit this field."New value: +"Optional image attachments supplied through the host's file upload support. The host supplies file_id and download_url. Map each attachment to a website path in assets: with one attachment, path alone is sufficient; with multiple attachments, use fileIndex. The assistant does not need to know generated file IDs or download URLs. Temporary URLs are import sources, not hosted image URLs. Clients without file input support can omit this field."

First observedSep 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description reveals important side effects and failure modes: it consumes the account creation allowance, returns a management link for configuration, can fail with requires_adaptation/requires_entitlement and publicationPerformed false, imports and hosts its own copy of images, and explicitly lists unsupported formats. This is far more than the annotations convey.

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?

The description is long but every sentence carries necessary information. It front-loads the primary purpose, then methodically addresses allowances, workspace selection, image handling, error cases, and limitations. Given the tool's complexity (9 parameters, multiple edge cases), this density is justified and not redundant.

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?

The description covers all critical aspects for a publishing tool: return artifacts (live and management links), side effects (allowance consumption), constraints (image handling, unsupported formats), and error outcomes (validation failures). The presence of an output schema reduces the need to explain return values, and the description sufficiently contextualizes the tool within its siblings.

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?

The schema description coverage is 100%, so the baseline is 3. The tool description adds value by explaining the relationship between imageFiles and assets (path alone vs. fileIndex), reinforcing the rule to never invent file IDs, and clarifying that sharingMode only supports 'public'. These clarifications go beyond the schema, so a 4 is warranted.

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 opens with a precise verb and resource: 'Publishes supplied HTML as a new public Carryo website' and enumerates the intended use cases (presentation, proposal, report, etc.). It also distinguishes itself from siblings by noting it creates a new website and returns live and management links, making it unmistakable from edit, unpublish, or save_draft.

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?

The description gives practical guidance: it explains when to attach images via imageFiles vs. assets, warns against inventing file IDs, notes that Personal is the default destination and workspaceId selects a team, and cautions about the account creation allowance. It also flags unsupported inputs (base64, data URLs). While it doesn't explicitly compare to sibling tools like website.save_draft, the context (new publication, no mention of drafts) implies the right usage.

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

All Carryo Website Publisher 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?