Put It Online

Publish a web page or site

publish_site

Put a web page or small static site you created online instantly. Pass {"files": {"index.html": "…", "style.css": "…", "app.js": "…"}} (paths relative to the site root; index.html required). Images can go in base64_files. Returns the public URL. Pages are served sandboxed on their own link.

Input Schema

Name	Required	Description
`slug`	No	Custom link name (3-40 letters, digits, dashes); available on plans with custom names.
`files`	Yes	Map of path -> text content, e.g. {"index.html": "<!doctype html>…", "style.css": "body{…}"}. Must include index.html.
`title`	No	Name for the site (shown in the dashboard).
`password`	No	Visitors must enter this password to open the link; available on plans with password protection.
`base64_files`	No	Optional map of path -> base64 content for binary assets such as images.

Output Schema

Name	Required	Description
`url`	Yes	The public link to share.
`kind`	Yes	html \| site \| file \| bundle \| pending
`slug`	Yes
`title`	Yes
`views`	Yes	View count; null when the link's account plan has no view counts, or the link has no account.
`status`	Yes	checking = not live yet (poll get_link); live = shareable; unpublished = not published; publishing = will be live soon (poll get_link); in_review = not available right now; removed = removed by moderation (see removed_reason, appeal_url).
`permanent`	Yes
`appeal_url`	No	Only with status removed: mailto link to appeal to abuse@putit.online.
`created_at`	Yes
`expires_at`	Yes	ISO time the link stops working; null for permanent links.
`file_count`	Yes
`manage_url`	No	Private page to manage/delete the link. Only returned on creation; keep it secret.
`size_bytes`	Yes
`content_url`	No	Only when live, for sites and single files: where the content itself is served (https://<slug>.putitcdn.com/…). Share `url` instead; it always works.
`checkout_url`	No	Only with status unpublished: the page where the uploader can publish this link.
`manage_token`	No	Secret token returned on creation for every new link (keep it secret). Anonymous callers pass it to get_link/delete_link; a link in an account is managed by that account instead.
`removed_reason`	No	Only with status removed: why, in plain words.
`status_message`	Yes
`removed_category`	No	Only with status removed: the moderation category (malware, phishing, explicit, …); null when not disclosed.
`password_protected`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 19, 2026

changedOutput schema / properties / manage_token / description

Previous value: -"Secret token for get_link/delete_link without an account. Only returned on creation."New value: +"Secret token returned on creation for every new link (keep it secret). Anonymous callers pass it to get_link/delete_link; a link in an account is managed by that account instead."

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / content_url

Added value: +{
+  "description": "Only when live, for sites and single files: where the content itself is served (https://<slug>.putitcdn.com/…). Share `url` instead; it always works.",
+  "type": "string"
+}

First observedOct 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With annotations already declaring the write/non-destructive/open-world profile, the description adds useful behavioral details: pages are served sandboxed on their own link, the public URL is returned, and index.html is required. It still omits auth needs, rate limits, and what happens on republish, but the added context is valuable.

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 front-loaded with purpose and usage, and every sentence earns its place by covering the required file structure, binary assets, return value, and serving behavior. It is appropriately sized with no wasted wording.

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?

Given the rich schema (100% coverage), annotations, and an output schema, the description covers the essential call behavior: what it does, required index.html, optional base64 files, and where the content is served. It does not address optional parameters like slug, title, or password, but those are fully documented in the schema.

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 all five parameters thoroughly. The description repeats the files example and says images can go in base64_files, but adds no syntax or format details beyond what the schema provides.

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?

The description states a specific verb ('Put ... online instantly') and resource ('a web page or small static site you created'). It does not distinguish this tool from siblings like upload_file or create_upload_session, so the agent must infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a page or site you created, but provides no explicit when-to-use conditions, prerequisites, or alternatives. No guidance on when to choose this over upload_file or create_upload_session is given.

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

All Put It Online 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.