Skip to main content
Glama

Pagetool

Publish a site to a domain

publish_site
Destructive

Puts a finished site live on the domain the user has connected. publish_site takes no payment itself; it requires a signed-in account with the pagetool.sites.write scope and either an active plan or an open free trial. Everything before it - building, editing, theming, previewing - is free and account-free, so build first and come here only when the user says they want to keep the site.

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": {
      "site_key": "<site_key>",
      "domain": "<domain>"
    },
    "name": "publish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe domain to publish to, e.g. "example.com".
site_keyYesThe site to publish.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description adds real context beyond the annotations: authentication requirement, required scope, plan/trial gating, and the clarification that no payment is taken here. With destructiveHint=true and openWorldHint=true already declared, the remaining gap is that it does not say what the publish displaces or how a failed publish is recovered.

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

Conciseness5/5

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

Three sentences, front-loaded with the action, then the prerequisites, then the sequencing advice. Every sentence carries decision-relevant information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should say what a successful publish yields (live URL, deployment state) and what failure looks like given destructiveHint and non-idempotent behavior. Preconditions and sequencing are complete, but the outcome side is missing.

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 both domain and site_key are already documented in the input schema. The description adds no constraint, format, or validation detail about either parameter, which is the expected baseline-3 outcome when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Puts a finished site live on the domain the user has connected" is a specific verb plus resource with a clear end state. It implicitly separates publishing from the free build/edit/preview stages, but it never names sibling tools such as publish_staged or publish_status, so an agent must still infer which publish variant applies.

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?

Strong when-to-use guidance: build first, then come here only when the user explicitly wants to keep the site. It also states the gating conditions (signed-in account with pagetool.sites.write scope, active plan or open free trial). It stops short of naming an alternative for staged/draft publishing.

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