Skip to main content
Glama

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

by site.yeetit

update_website

Update an existing published website with new HTML content. Requires authentication via edit_key (from the original publish response) or api_key (from the user's dashboard after claiming the site). The html field replaces the entire page — this is a full replacement, not a patch. You can also update assets. Use this when a user asks you to modify, edit, or change a site you previously published. IMPORTANT: You must provide either edit_key or api_key for authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
htmlYesComplete HTML document to replace the existing page with. Must be a valid, self-contained page. This replaces the entire page content.
slugYesThe slug of the site to update (e.g. "hello-world-k3m").
titleNoOptional new title for the page.
assetsNoOptional map of filename to content. If provided, replaces ALL existing assets. Omit to keep existing assets unchanged.
api_keyNoThe user's API key from their dashboard (e.g. "yt_abc123..."). Use this if the user has claimed the site and provided their API key.
edit_keyNoThe edit key returned when the site was originally published (e.g. "ek_9c4d2e7f..."). Use this if you still have it from the publish response.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses authentication via edit_key or api_key, emphasizes full replacement rather than patch, and mentions asset updates. These add context beyond the schema, though it omits response behavior and failure modes.

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?

Front-loaded with the primary purpose and generally compact. However, the authentication requirement is stated twice ('Requires authentication...' and 'IMPORTANT: You must provide...'), creating minor redundancy. Otherwise every sentence earns its place.

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?

For a 6-param tool with no annotations and no output schema, the description covers purpose, authentication, replacement semantics, and asset updates. It does not explain return values or error handling, but the core operational context is well addressed. Optional parameters like title are left to the schema.

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%, so baseline is 3. Description adds value by clarifying the html field is a full replacement and stressing the requirement for either edit_key or api_key. These insights supplement rather than merely repeat 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?

States the verb 'update', the resource 'existing published website', and the input 'new HTML content'. Distinct from sibling tools by emphasizing 'existing published' and 'previously published', clearly differentiating from publish_website.

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?

Provides explicit usage context: 'Use this when a user asks you to modify, edit, or change a site you previously published.' Includes authentication requirements and full-replacement semantics. Does not explicitly name alternatives or exclusions, so not a 5.

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. 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 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