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. Image assets use relative HTML paths and exactly one source: a fileId matching a host-supplied imageFiles attachment, or a fetchable HTTP(S) sourceUrl. 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 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.
`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 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.
`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.

First observedSep 10, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations indicate it's a write operation (readOnlyHint=false) with side effects (openWorldHint=true). The description adds critical context: it consumes the account creation allowance, imports and hosts its own copy of images, returns live and management links, and can return validation errors (requires_adaptation/requires_entitlement) with publicationPerformed false. It also highlights limitations (no backend hosting) that go beyond annotations. Loses a point because it could mention the side effect of overwriting any existing site with the same slug? But not required as this is creation.

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?

The description is dense but each sentence earns its place. It front-loads the core purpose and use cases, then covers key constraints (account allowance, image handling, validation failures) without fluff. It is longer than typical but every part adds critical information that is not in the schema.

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?

With an output schema present)Skip the return details are covered. The description covers all necessary aspects for correct invocation: prerequisites (account allowance), parameter semantics (assets), error handling (validation errors), and scope limitations (only HTML pages, no backend). It leaves nothing significant to guess.

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 description coverage is 100%, so baseline is 3. The description adds meaning by explaining how assets must be set up (relative HTML paths, exactly one source, base64 unsupported), how forms work (window.CarryoForms.submit), and the behavior of imageFiles (temporary download URLs). It clarifies customSlug generation and the role of expiresAt. Already high, so 4 is warranted for the extra depth.

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 clearly states the tool publishes supplied HTML as a new public Carryo website, listing specific use cases (presentation, proposal, report, etc.) and contrasting with siblings like website.edit (for editing) and website.save_draft (for drafts). It distinguishes itself by the 'new' and 'public' aspects.

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?

The description explicitly states the default destination is Personal and that workspaceId is used for a user-chosen team, and mentions checking account creation allowance. It does not explicitly name alternatives for when not to use, but the sibling list (website.edit, website.save_draft) context implies this is for creation. It also notes what is unsupported (general file storage, backend hosting) to prevent misuse.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?