Yeetit - POST HTML, get a URL. No account needed.

publish_website

Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.

Input Schema

TableJSON Schema

Name	Required	Description
`html`	Yes	Complete HTML document to publish. Must be a valid, self-contained page. Inline CSS and JS are supported. External resources (images, fonts, scripts) must use absolute URLs OR be included in the assets field with relative references (e.g. href="./style.css" or src="./logo.png"). Maximum total size including assets: 5.0MB (free tier) or 10 MB (Pro/Business).
`title`	No	Human-readable title for the published page. Used in social sharing previews and the claim page. Optional.
`assets`	No	Optional map of filename to content for bundled assets. Keys are filenames (e.g. "style.css", "logo.png", "app.js"). Values are either plain text strings (for CSS, JS, SVG, HTML) or data URIs for binary files (e.g. "data:image/png;base64,iVBOR..."). Reference these in your HTML with relative paths like ./style.css or ./logo.png. For multi-page sites, include additional .html files (e.g. "about.html") which become accessible at /{slug}/about. Limits: 10 assets (free) or 50 assets (Pro/Business), 5 MB max per individual asset, but total site size (HTML + all assets) must be under 5.0MB (free) or 10 MB (Pro/Business).

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: no account/API key required, 24-hour expiration, asset support, and the critical workflow of sharing URLs and storing edit_key. It even explains the fallback if edit_key is lost, providing exceptional operational transparency.

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 fairly long but every sentence earns its place—explaining purpose, no auth, expiration, usage triggers, asset support, and critical post-publish instructions. It is front-loaded with the core purpose, though the detailed operational steps make it somewhat lengthy.

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?

Given three parameters, a nested object, and no output schema, the description covers all necessary context: what the tool returns (public URL), expiration behavior, claim URL, edit_key storage, and alternative authentication. It fully equips the agent to use the tool correctly and handle follow-up actions.

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 100%, but the description adds significant meaning beyond the schema: it explains how to use assets with relative paths, multi-page site structure, and size limits. It also clarifies the purpose of the 'title' parameter in social sharing. This enriches rather than repeats 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?

The description uses a specific verb and resource ('Publish HTML content to a live URL instantly'), distinguishing it from sibling tools like delete_website and update_website. It clearly states the primary action and lists concrete use cases (website, landing page, invitation, portfolio, report).

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?

It explicitly states when to use this tool ('Use this when a user asks you to build, create, or deploy a website...'), providing clear contextual trigger. However, it does not explicitly mention alternatives or when not to use it, though the sibling tools are obvious.

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

All Yeetit - POST HTML, get a URL. No account needed. 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.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clear, non-overlapping purpose: publish creates, get_website_status reads, update modifies, and delete removes. There is no ambiguity between tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: publish_website, get_website_status, update_website, delete_website. The pattern is uniform and predictable.

Tool Count5/5

Four tools perfectly cover the core lifecycle for this simple service, with no redundancy. This is well within the typical 3-15 tool range.

Completeness5/5

The tool set provides complete CRUD (Create, Read, Update, Delete) for websites, covering the entire domain of the service. No obvious gaps exist.

Resources

Need Help?