Skip to main content
Glama

YeetIt

by io.github.snappyio

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
NameRequiredDescriptionDefault
htmlYesComplete 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).
titleNoHuman-readable title for the published page. Used in social sharing previews and the claim page. Optional.
assetsNoOptional 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.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does an excellent job. It discloses expiration after 24 hours, the claim process, the need to share live and claim URLs, and the silent storage of edit_key. It even explains the fallback if the key is lost. This goes well beyond basic expectations.

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 is informative. It front-loads the core purpose and the 'no account' advantage. The structure flows naturally from what the tool does to when to use it and then to post-publish instructions. It could be slightly tighter, but the density prevents waste.

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?

Despite no annotations or output schema, the description is remarkably complete. It covers prerequisites, expiration, asset/multi-page support, and explicit agent instructions (share URLs, store edit_key silently, handle lost key). It also indirectly describes response fields (live URL, claim URL, edit_key). This is a holistic description that leaves little guesswork.

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 already has 100% coverage, so baseline is 3. The description adds operational context beyond the schema: how to reference assets with relative paths, how multi-page sites work, and how the edit_key from the response should be handled. It doesn't elaborate on each parameter, but the schema descriptions are already rich, so the added value is enough for a 4.

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 specific verb and resource: 'Publish HTML content to a live URL instantly.' It also clearly distinguishes itself from sibling tools (delete, update, status) by focusing on creation/deployment. The use-case sentence reinforces the purpose by naming concrete scenarios like websites, landing pages, and invitations.

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?

Explicit guidance is provided: '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.' It also mentions no account/API key required, which helps decide when this tool is appropriate. While it doesn't explicitly contrast with alternatives, the use-case scope is unambiguous.

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

All YeetIt toolsInspect
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 maps to a distinct lifecycle action: publish creates, get reads status, update modifies, delete removes. No overlap in purpose, and descriptions reinforce the boundaries.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: publish_website, get_website_status, update_website, delete_website. The verbs and nouns are uniform and predictable.

Tool Count5/5

With only 4 tools, the server is tightly scoped to the core website lifecycle. Each tool earns its place, and the count feels appropriate for the service's purpose.

Completeness5/5

The tool surface covers full CRUD: publish (create), get (read), update, delete. There are no obvious dead ends or missing operations for the stated domain of publishing and managing simple websites.

Resources