Skip to main content
Glama

Publish a site

publish_site
Destructive

Publishes websites, HTML games, interactive demos, reports, and other AI-created content to a public HTTPS URL at a slug. Inputs: files (required), and optional slug, spa, ttl_seconds, merge, expected_version, via, heard_from, token, listed, category, tags, title, and description. Paths are stored exactly. Returns url, path_url, slug, version, listing, analytics_url (the owner visit page on deed.page), and token on the first anonymous publish. On deed.page, url and path_url are both https://{slug}.deed.page/. A lost token has no recovery unless an optional recovery email was attached. When expected_version does not match the live version, the result is version_conflict and nothing is written. A racing publish of the same slug returns version_conflict even without expected_version. Malware, executables, credential-harvesting pages, and tunnel-redirect pages return content_rejected and are not stored. Content policy: no real-money gambling, phishing, malware, scams or referral spam, tunnel redirects, or illegal content; see https://deed.page/acceptable-use. .bin is blocked by file type (it often has no MZ or ELF header). A raw octet-stream body is screened as one file. listed defaults to false, so the slug stays out of the public gallery unless listed is true. Password-protected sites cannot be listed. Once per owner, a Free site that shows the badge may also return clean_publish, an optional $9 one-time offer to remove the badge from that site: pass its user_message to your human once; never pay without their explicit approval. If the files total more than about 3.5 MB, do not call publish_site. Call plan_upload, run commands in a shell, then finalize_upload. Or run node publish-large.mjs <dir> (https://deed.page/cli/publish-large.mjs).

Input Schema

NameRequiredDescriptionDefault
spaNoServe index.html for unknown paths (single-page apps).
viaNoOptional label stored with the publish. At most 80 characters. An IP address, a URL, or an email address is not stored. A non-empty value replaces the X-Via header.
slugNoExact slug matching ^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$ (lowercase letters, digits, hyphens, 1-63, no leading or trailing hyphen). Invalid slugs return slug_invalid and are not rewritten. Reserved names (hello, my-page, www, api, docs, admin, mcp, blog, app, status, and other docs examples) return slug_reserved on a new claim. A token that already owns one can still update it. Omit for a random slug.
tagsNoUp to 5 tags. Each tag is lowercase letters, digits, and hyphens, at most 32 characters.
filesYesPath map, or an array of {path, content} or {path, base64}. Paths are stored exactly as given (a single top-level directory is not removed). Text as a string, binary as {"base64":"..."}. Example: {"index.html":"<!doctype html><h1>Hi</h1>","img/logo.png":{"base64":"iVBOR..."}}. Any other array is rejected.
mergeNoAdd or overwrite only these exact paths on the existing site. Paths omitted from this call are left unchanged. Nothing is moved to the site root.
titleNoGallery title, at most 80 characters. Required when listed is true.
tokenNoBearer token returned by your first publish (deed_tok_...). Optional if the MCP client sends Authorization: Bearer.
listedNoOpt into the public gallery. Default false. false removes the slug immediately. Password-protected sites cannot be listed.
categoryNoGallery category. Required when listed is true.
heard_fromNoOptional. Where you or your user found deed.page, such as a skill repo, a directory, a blog post, X, or a friend. Free text, at most 200 characters. An email address, IP address, or phone number is stored as [redacted]. A URL or hostname is kept. Omit it and signup continues.
descriptionNoGallery description, at most 300 characters. Required when listed is true.
ttl_secondsNoOpt-in expiry in seconds. Omit for a permanent site.
idempotency_keyNoOptional retry key, 16-255 visible ASCII characters (a random UUID works). If this call fails with a connection reset, a timeout, or a 502 or 503, call it once more with the same arguments and the same idempotency_key: a publish that already went through is replayed (same slug, same version, same token, idempotent_replayed: true) instead of being written twice. The Idempotency-Key HTTP header works the same way.
expected_versionNoLive version this write is based on, such as "v3". If the slug is no longer at that version, the result is version_conflict and nothing is written. A racing publish of the same slug returns version_conflict even when this is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "Optional retry key, 16-255 visible ASCII characters (a random UUID works). If this call fails with a connection reset, a timeout, or a 502 or 503, call it once more with the same arguments and the same idempotency_key: a publish that already went through is replayed (same slug, same version, same token, idempotent_replayed: true) instead of being written twice. The Idempotency-Key HTTP header works the same way.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / heard_from
      Added value: +{
      +  "description": "Optional. Where you or your user found deed.page, such as a skill repo, a directory, a blog post, X, or a friend. Free text, at most 200 characters. An email address, IP address, or phone number is stored as [redacted]. A URL or hostname is kept. Omit it and signup continues.",
      +  "type": "string"
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Gallery category. Required when listed is true.",
      +  "enum": [
      +    "Apps & tools",
      +    "Games",
      +    "Business",
      +    "Portfolio",
      +    "Docs & guides",
      +    "Education",
      +    "Events",
      +    "Other"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "Gallery description, at most 300 characters. Required when listed is true.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / listed
      Added value: +{
      +  "description": "Opt into the public gallery. Default false. false removes the slug immediately. Password-protected sites cannot be listed.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tags
      Added value: +{
      +  "description": "Up to 5 tags. Each tag is lowercase letters, digits, and hyphens, at most 32 characters.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 5,
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "Gallery title, at most 80 characters. Required when listed is true.",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
      +  "description": "Optional label stored with the publish. At most 80 characters. An IP address, a URL, or an email address is not stored. A non-empty value replaces the X-Via header.",
      +  "type": "string"
      +}
  5. Changed2 schema fields changed
    • changedInput schema / properties / expected_version / description
      Previous value: -"Live version this write is based on, such as \"v3\", from the last publish or get_site. If the slug is no longer at that version, the call returns version_conflict and does not write. Racing publishes fail the same way even when this is omitted."New value: +"Live version this write is based on, such as \"v3\". If the slug is no longer at that version, the result is version_conflict and nothing is written. A racing publish of the same slug returns version_conflict even when this is omitted."
    • changedInput schema / properties / files / description
      Previous value: -"Map of relative path to file contents. Paths are stored exactly as given (a single top-level directory is not removed). Text as a string, binary as {\"base64\":\"...\"}. Example: {\"index.html\":\"<!doctype html><h1>Hi</h1>\",\"img/logo.png\":{\"base64\":\"iVBOR...\"}}"New value: +"Path map, or an array of {path, content} or {path, base64}. Paths are stored exactly as given (a single top-level directory is not removed). Text as a string, binary as {\"base64\":\"...\"}. Example: {\"index.html\":\"<!doctype html><h1>Hi</h1>\",\"img/logo.png\":{\"base64\":\"iVBOR...\"}}. Any other array is rejected."
  6. Changed1 schema field changed
    • addedInput schema / properties / expected_version
      Added value: +{
      +  "description": "Live version this write is based on, such as \"v3\", from the last publish or get_site. If the slug is no longer at that version, the call returns version_conflict and does not write. Racing publishes fail the same way even when this is omitted.",
      +  "type": "string"
      +}
  7. Changed3 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"Map of relative path to file contents. Text as a string, binary as {\"base64\":\"...\"}. Example: {\"index.html\":\"<!doctype html><h1>Hi</h1>\",\"img/logo.png\":{\"base64\":\"iVBOR...\"}}"New value: +"Map of relative path to file contents. Paths are stored exactly as given (a single top-level directory is not removed). Text as a string, binary as {\"base64\":\"...\"}. Example: {\"index.html\":\"<!doctype html><h1>Hi</h1>\",\"img/logo.png\":{\"base64\":\"iVBOR...\"}}"
    • changedInput schema / properties / merge / description
      Previous value: -"Add these files to the existing site instead of replacing it."New value: +"Add or overwrite only these exact paths on the existing site. Paths omitted from this call are left unchanged. Nothing is moved to the site root."
    • changedInput schema / properties / slug / description
      Previous value: -"Lowercase letters, digits, hyphens (1-63). Omit for a random slug."New value: +"Exact slug matching ^[a-z0-9](?:[a-z0-9-]{0,61}[a-z0-9])?$ (lowercase letters, digits, hyphens, 1-63, no leading or trailing hyphen). Invalid slugs return slug_invalid and are not rewritten. Reserved names (hello, my-page, www, api, docs, admin, mcp, blog, app, status, and other docs examples) return slug_reserved on a new claim. A token that already owns one can still update it. Omit for a random slug."
  8. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing version_conflict semantics (including racing publishes without expected_version), content_rejected for malware/tunnel redirects/credential harvesting, the acceptable-use policy, that .bin is blocked by file type, that a lost token is unrecoverable, and the badge-removal upsell rule requiring human approval before payment. Annotations only mark it destructive/open-world; the description supplies the actual risk and failure surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One long undifferentiated paragraph that front-loads a redundant parameter inventory while burying the operationally critical 3.5 MB limit and the plan_upload alternative at the very end. Content policy, billing upsell, token recovery, and file-type screening are interleaved with no structure, and 'listed defaults to false' duplicates a constraint also stated in the schema.

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 15-parameter write tool with no output schema, the description compensates by naming the return fields (url, path_url, slug, version, listing, analytics_url, token), documenting the domain-specific URL shape, and covering the main error outcomes. An agent has what it needs to call this correctly or to route to plan_upload.

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 coverage is 100%, so the schema already documents every parameter in depth; the description mostly restates the parameter names in a list. It adds a small amount of extra meaning (listed defaults to false keeps the slug out of the gallery, password-protected sites cannot be listed, a recovery email may be attached to a token), but most of the semantics live in 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?

Opens with a specific verb and resource ('Publishes websites... to a public HTTPS URL at a slug') and enumerates the content types it accepts (games, demos, reports), which distinguishes it from siblings like update_site or set_listing that modify metadata rather than content.

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?

Gives an explicit when-not and names the alternatives: 'If the files total more than about 3.5 MB, do not call publish_site. Call plan_upload, run `commands`, then finalize_upload.' It also implies the merge path for updating existing paths. What is missing is routing guidance against siblings such as update_site or set_listing for metadata-only changes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.