Skip to main content
Glama

Publish a website

publish_site
Destructive

Publish files as a live website, served over HTTPS at its own URL. Use it when the user asks to publish, host, or share a report, page, dashboard, or other static files at a URL. Naming Valet only chooses where; it is not a request to publish. Honor an artifact form the user requests; otherwise choose the form and treatment from its audience, job, and material. A request for a live URL chooses delivery, not one long scrolling page.

Read the organization's requirements with get_skill governance before calling. A policy set to block refuses a publish that fails it, and the answer names what to fix; a monitor policy only records findings, which get_evaluation lists.

title and description are required on every publish of files. Write them for the person who comes back to this page in a month: the site's name is only part of its URL.

files suits a few small text pages (HTML, CSS, JavaScript, Markdown, JSON, SVG). For a large site or binary assets, call create_push, push with git, and pass push instead.

Publishing changes the content of a permanent site that already exists: create it first with create_service (kind: site), then publish to its name. It leaves the site's access mode and shares as they are; set_service_access and share_service change them.

Returns the site's URL and access mode, the version that went live, and the release's evaluation when it has one. In an organization with release policies, an account publish answers with evaluation and no version: the release waits for its policies, and get_evaluation follows it. Files or a push whose tree the site already serves answer no_changes and publish nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "publish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files.
pushNoPublish a Git push instead of files: the id create_push returned and the commit you pushed to its branch. Use it when you can run git with network access, because it sends only what changed. Every other argument keeps its meaning.
filesNoThe site's files. Give this or push, not both. Include index.html, the page the site's URL opens; add more for stylesheets, scripts, or further pages.
titleNoWhat the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says.
org_nameNoThe Valet organization to publish into. Omit to use the organization the account joined first.
descriptionNoOne sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed.
idempotency_keyNoAn opaque key of your choosing. Repeating a call with the same key returns the first call's result instead of publishing again, which makes a retry safe.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
urlNoURL that serves the site. Absent while the site has no route.
nameYesName of the site. It is the first label of its URL.
accessYesWho can open the site: public, private, or password. Change it with set_service_access.
versionNoVersion number of the release the publish made live. Absent when no release went live: the release waits for its policies (see evaluation) or nothing changed.
evaluationNoThe release evaluation. Without version, the release waits for its policies: follow it with get_evaluation. With version, the release is live and this is its monitor-only evaluation. Absent when the release has none.
no_changesNoTrue when the files or pushed tree are what the site already serves, so nothing was published. Absent otherwise.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / no_changes / description
      Previous value: -"True when the pushed tree is what the site already serves, so nothing was published. Absent otherwise."New value: +"True when the files or pushed tree are what the site already serves, so nothing was published. Absent otherwise."
  2. Changed1 schema field changed
    • changedInput schema / properties / push / description
      Previous value: -"Publish a Git push instead of files: the id create_push returned and the commit you pushed to its branch. Use it when you can run git with network access, because it sends only what changed. Pass files or push, not both; every other argument keeps its meaning."New value: +"Publish a Git push instead of files: the id create_push returned and the commit you pushed to its branch. Use it when you can run git with network access, because it sends only what changed. Every other argument keeps its meaning."
  3. Changed3 schema fields changed
    • changedOutput schema / properties / evaluation / properties / deploy_message / description
      Previous value: -"The refusal's message when deploy refused the release. Absent otherwise."New value: +"The refusal's message when deploy refused the release, with credentials redacted as [redacted]. Absent otherwise."
    • addedOutput schema / properties / evaluation / properties / redactions
      Added value: +{
      +  "description": "How many credentials were replaced with [redacted] in the text this answer was built from: secret values the service holds, and strings shaped like an API key, a private key, a token, or a password in a URL or header. Redaction is best effort, so 0 does not prove the text holds no credential.",
      +  "type": "integer"
      +}
    • changedOutput schema / properties / evaluation / required
      Previous value: -[
      -  "id",
      -  "status"
      -]New value: +[
      +  "id",
      +  "status",
      +  "redactions"
      +]
  4. Changed3 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"With files, a call without it is refused. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."New value: +"One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."
    • changedInput schema / properties / files / items / properties / path / description
      Previous value: -"Path relative to the site root, with '/' separators and no leading slash: index.html, styles/main.css. It may not contain '.' or '..' segments."New value: +"Path of the file relative to the site root, such as index.html or styles/main.css."
    • changedInput schema / properties / title / description
      Previous value: -"With files, a call without it is refused. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."New value: +"What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."
  5. Changed1 schema field changed
    • changedInput schema / properties / files / description
      Previous value: -"The site's files. Give this or push, not both. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."New value: +"The site's files. Give this or push, not both. Include index.html, the page the site's URL opens; add more for stylesheets, scripts, or further pages."
  6. Changed25 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Required with files. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."New value: +"With files, a call without it is refused. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."
    • changedInput schema / properties / files / description
      Previous value: -"Required unless push is given. The site's files. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."New value: +"The site's files. Give this or push, not both. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."
    • changedInput schema / properties / files / items / properties / content / description
      Previous value: -"Required. The file's complete text content."New value: +"The file's complete text content."
    • changedInput schema / properties / files / items / properties / path / description
      Previous value: -"Required. Path within the site, relative and with no leading slash: index.html, styles/main.css. It may not contain '..'."New value: +"Path relative to the site root, with '/' separators and no leading slash: index.html, styles/main.css. It may not contain '.' or '..' segments."
    • changedInput schema / properties / name / description
      Previous value: -"The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files. Required."New value: +"The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files."
    • addedInput schema / properties / name / maxLength
      Added value: +63
    • addedInput schema / properties / name / minLength
      Added value: +3
    • addedInput schema / properties / name / pattern
      Added value: +"^[A-Za-z0-9][A-Za-z0-9-]{1,61}[A-Za-z0-9]$"
    • changedInput schema / properties / push / properties / commit / description
      Previous value: -"Required. The full sha of the commit you pushed to the push's branch. The recipe create_push returned prints it."New value: +"The full sha of the commit you pushed to the push's branch. The recipe create_push returned prints it."
    • changedInput schema / properties / push / properties / id / description
      Previous value: -"Required. The push_id create_push returned."New value: +"The push_id create_push returned."
    • changedInput schema / properties / title / description
      Previous value: -"Required with files. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."New value: +"With files, a call without it is refused. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."
    • addedInput schema / required
      Added value: +[
      +  "name"
      +]
    • addedOutput schema / properties / access / description
      Added value: +"Who can open the site: public, private, or password. Change it with set_service_access."
    • addedOutput schema / properties / evaluation / description
      Added value: +"The release evaluation. Without version, the release waits for its policies: follow it with get_evaluation. With version, the release is live and this is its monitor-only evaluation. Absent when the release has none."
    • addedOutput schema / properties / evaluation / properties / deploy / description
      Added value: +"What deploy did with the release: 'waiting' for the policies, 'live', or the code of the refusal. Absent when deploy has not decided."
    • addedOutput schema / properties / evaluation / properties / deploy_message / description
      Added value: +"The refusal's message when deploy refused the release. Absent otherwise."
    • addedOutput schema / properties / evaluation / properties / id / description
      Added value: +"ID of the release evaluation. Pass it to get_evaluation as evaluation_id."
    • addedOutput schema / properties / evaluation / properties / monitor_findings / description
      Added value: +"Count of findings monitor policies reported on a live release. They never block it; get_evaluation shows each. Absent when zero."
    • addedOutput schema / properties / evaluation / properties / monitor_running / description
      Added value: +"Names of monitor policies still pending or running on a live release. They never block it. Absent when none are."
    • addedOutput schema / properties / evaluation / properties / status / description
      Added value: +"Status of the evaluation across its release policies. get_evaluation lists the per-policy results."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the site. It is the first label of its URL."
    • addedOutput schema / properties / no_changes / description
      Added value: +"True when the pushed tree is what the site already serves, so nothing was published. Absent otherwise."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
    • addedOutput schema / properties / url / description
      Added value: +"URL that serves the site. Absent while the site has no route."
    • addedOutput schema / properties / version / description
      Added value: +"Version number of the release the publish made live. Absent when no release went live: the release waits for its policies (see evaluation) or nothing changed."
  7. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "name",
      -  "version",
      -  "access"
      -]New value: +[
      +  "org",
      +  "name",
      +  "access"
      +]
  8. Changed8 schema fields changed
    • removedInput schema / properties / anonymous
      Removed value: -{
      -  "description": "Set true only when the user explicitly wants a temporary public site without account ownership. Omit for the account-first path, which connects a Valet account when needed.",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / name / description
      Previous value: -"The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files. Required with a connected Valet account; leave it out for an anonymous publish."New value: +"The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files. Required."
    • removedInput schema / properties / site_token
      Removed value: -{
      -  "description": "The token an earlier anonymous publish returned. Give it back to update that same site instead of creating another.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / claim_url
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / created
      Removed value: -{
      -  "type": "boolean"
      -}
    • removedOutput schema / properties / expires_at
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / site_token
      Removed value: -{
      -  "type": "string"
      -}
    • changedOutput schema / required
      Previous value: -[
      -  "org",
      -  "name",
      -  "version",
      -  "access",
      -  "created"
      -]New value: +[
      +  "org",
      +  "name",
      +  "version",
      +  "access"
      +]
  9. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "access": {
      +      "type": "string"
      +    },
      +    "claim_url": {
      +      "type": "string"
      +    },
      +    "created": {
      +      "type": "boolean"
      +    },
      +    "evaluation": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "deploy": {
      +          "type": "string"
      +        },
      +        "deploy_message": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "string"
      +        },
      +        "monitor_findings": {
      +          "type": "integer"
      +        },
      +        "monitor_running": {
      +          "items": {
      +            "type": "string"
      +          },
      +          "type": [
      +            "null",
      +            "array"
      +          ]
      +        },
      +        "status": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "status"
      +      ],
      +      "type": [
      +        "null",
      +        "object"
      +      ]
      +    },
      +    "expires_at": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "no_changes": {
      +      "type": "boolean"
      +    },
      +    "org": {
      +      "type": "string"
      +    },
      +    "site_token": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "version": {
      +      "maximum": 2147483647,
      +      "minimum": -2147483648,
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "version",
      +    "access",
      +    "created"
      +  ],
      +  "type": "object"
      +}
  10. Changed7 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"Required. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."New value: +"Required with files. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."
    • changedInput schema / properties / files / description
      Previous value: -"Required. The site's files. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."New value: +"Required unless push is given. The site's files. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"An opaque key of your choosing. Repeating a call with the same key returns the first call's result instead of publishing a second site, which makes a retry safe."New value: +"An opaque key of your choosing. Repeating a call with the same key returns the first call's result instead of publishing again, which makes a retry safe."
    • changedInput schema / properties / name / description
      Previous value: -"The site's name, which becomes the first label of its URL, https://<name>.<org>.valet.run. Omit to have one generated. Naming a site that already exists republishes it. Requires a connected Valet account."New value: +"The site's name, which is the first label of its URL, https://<name>.<org>.valet.run. The site must exist: create it first with create_service. Publishing to it replaces its files. Required with a connected Valet account; leave it out for an anonymous publish."
    • addedInput schema / properties / push
      Added value: +{
      +  "description": "Publish a Git push instead of files: the id create_push returned and the commit you pushed to its branch. Use it when you can run git with network access, because it sends only what changed. Pass files or push, not both; every other argument keeps its meaning.",
      +  "properties": {
      +    "commit": {
      +      "description": "Required. The full sha of the commit you pushed to the push's branch. The recipe create_push returned prints it.",
      +      "type": "string"
      +    },
      +    "id": {
      +      "description": "Required. The push_id create_push returned.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "commit"
      +  ],
      +  "type": "object"
      +}
    • changedInput schema / properties / title / description
      Previous value: -"Required. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."New value: +"Required with files. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."
    • removedInput schema / required
      Removed value: -[
      -  "files",
      -  "title",
      -  "description"
      -]
  11. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The site's name, which becomes the last segment of its URL, https://<org>.valet.run/<name>. Omit to have one generated. Naming a site that already exists republishes it. Requires a connected Valet account."New value: +"The site's name, which becomes the first label of its URL, https://<name>.<org>.valet.run. Omit to have one generated. Naming a site that already exists republishes it. Requires a connected Valet account."
  12. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"The site's name, which becomes part of its URL. Omit to have one generated. Naming a site that already exists republishes it. Requires a connected Valet account."New value: +"The site's name, which becomes the last segment of its URL, https://<org>.valet.run/<name>. Omit to have one generated. Naming a site that already exists republishes it. Requires a connected Valet account."
  13. Changed5 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."New value: +"Required. One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed."
    • changedInput schema / properties / files / description
      Previous value: -"The site's files. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."New value: +"Required. The site's files. One file named index.html is the minimum; add more for stylesheets, scripts, or further pages."
    • changedInput schema / properties / files / items / properties / content / description
      Previous value: -"The file's complete text content."New value: +"Required. The file's complete text content."
    • changedInput schema / properties / files / items / properties / path / description
      Previous value: -"Path within the site, relative and with no leading slash: index.html, styles/main.css. It may not contain '..'."New value: +"Required. Path within the site, relative and with no leading slash: index.html, styles/main.css. It may not contain '..'."
    • changedInput schema / properties / title / description
      Previous value: -"What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."New value: +"Required. What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says."
  14. Changed1 schema field changed
    • addedInput schema / properties / anonymous
      Added value: +{
      +  "description": "Set true only when the user explicitly wants a temporary public site without account ownership. Omit for the account-first path, which connects a Valet account when needed.",
      +  "type": "boolean"
      +}
  15. Changed3 schema fields changed
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "One sentence saying what the site holds, for a person deciding whether to open it. It is shown beside the title wherever the site is listed.",
      +  "maxLength": 1024,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "What the site is called, written for a person: 'Q3 Migration Audit', not a hostname. It labels the site wherever it is listed, so write the same thing the page's own <title> says.",
      +  "maxLength": 1024,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "files"
      -]New value: +[
      +  "files",
      +  "title",
      +  "description"
      +]
  16. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that publishing replaces files on an existing permanent site (consistent with destructiveHint=true), that it leaves access mode and shares untouched, how release policies change the response (evaluation without a version), and that identical trees return no_changes. It adds real operational context rather than restating readOnlyHint/openWorldHint.

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 purpose and the core exclusion, then organized into prerequisite, parameter choice, and return-value paragraphs that are each scannable. It is longer than strictly necessary — the sentences about choosing "form and treatment" from audience/job/material are somewhat editorial — but no paragraph is wasted.

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 destructive, open-world, nested-schema mutation tool, the description covers prerequisites, sibling alternatives, both input modes, side effects on existing site state, and both success and policy-deferred outcomes. An output schema exists, yet the return summary is still concrete enough that an agent knows what to report.

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, but the description goes further: it states that title and description are required on every file publish and explains why they matter, and it gives a decision rule for files vs push ("For a large site or binary assets, call create_push..."). It does not explain name as a URL label beyond the schema, so not a perfect 5.

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 first sentence states a specific verb and resource with scope: "Publish files as a live website, served over HTTPS at its own URL." It immediately distinguishes itself from adjacent tools (create_push for large/binary sites, create_service for creation, set_service_access/share_service for access), so an agent can route correctly without opening a schema.

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 when-to-use ("when the user asks to publish, host, or share a report, page, dashboard"), plus a negative case ("Naming Valet only chooses where; it is not a request to publish") and named alternatives for large sites and for permission changes. It also front-loads a prerequisite step (get_skill governance) with an explanation of what block vs monitor policies do.

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.

Resources