Skip to main content
Glama
thinhost

thinhost-mcp

Official
by thinhost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

update_website

Push updated pages and assets to an existing hosted website. Set sync=true for full site redeploys to delete stale files; use sync=false to edit selected pages.

Instructions

Push updated pages/assets to an existing hosted website (upsert by path).

Files present locally replace the same paths on the site. With sync=false (default) site files not in this upload are left untouched — right for editing a few pages by hand. With sync=true the upload is treated as the complete site: after it lands, every page and asset the site has that this upload does not is deleted. Always use sync=true when redeploying a generator build folder (Docusaurus, Astro, Vite, Next export) — each build renames its hashed chunks, and without sync the old ones pile up forever. Dashboard-authored redirect pages are kept regardless and listed in kept_redirects.

Use publish_website for a brand-new site.

Args: website: The site's id, slug, or live URL (e.g. "https://thin.host/s/my-site/"). source_path: Absolute path to an .html file, a site/build directory, or a .zip. title: Optional new site title. sync: Treat the upload as the whole site and remove everything else.

Returns: url plus updated counts, and with sync=true the removed_pages / removed_assets. framework, base_url, warning as in publish_website.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
syncNo
titleNo
websiteYes
source_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It clearly discloses destructive behavior with sync=true (deletes files not in upload), default behavior, and an exception (dashboard-authored redirect pages are kept). This is critical contextual information for a mutation tool.

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?

Information is well-organized with clear sections for Args and Returns. However, the behavioral paragraph is somewhat lengthy and could be tightened, though every sentence adds necessary context for this destructive operation.

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?

For a complex mutation tool without annotations or output schema, the description covers purpose, usage, destructive behavior, parameter meanings, return values, and alternative tools. It is complete enough for an agent to invoke correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain parameters. It does so thoroughly: defines website as id/slug/URL, source_path as .html/directory/.zip, and explains sync's effect. This compensates fully for the schema gap.

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?

Opens with a specific verb ('Push updated pages/assets'), names the resource ('existing hosted website'), and clarifies the upsert-by-path semantics. It explicitly distinguishes itself from publish_website ('Use publish_website for a brand-new site').

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?

Provides explicit when-to-use guidance for sync=true vs sync=false, including concrete frameworks (Docusaurus, Astro, Vite, Next export), and explains the risk of not using sync. It also names the alternative tool for new sites.

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

Deploy Server

Other Tools