Skip to main content
Glama

Publish a site

iter0_publish_site
DestructiveIdempotent

Puts a saved site live at its own free address, name.iter0.app, so anyone can open it. Free: it uses no credits. Takes the designId and, optionally, a name for the address (lowercase letters, numbers and hyphens, 3 to 63 characters; without one, iter0 uses the free address it suggests). Called without confirmationToken, nothing goes live: it returns the exact address and a confirmationToken. Called again with the same designId and that confirmationToken, it publishes, and the site becomes public. A confirmationToken cannot publish twice. If the site is already live and up to date it says so and needs no token. If the result says the outcome is unknown, iter0_publish_status shows whether the site is live. Only the site's owner can publish.

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": {
      "designId": "<designId>"
    },
    "name": "iter0_publish_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
designIdYesThe saved design, from iter0_get_design or iter0_list_my_designs.
subdomainNoThe name for the address: name.iter0.app. Optional; only on the first call, and only when the person chose a name.
confirmationTokenNoLeave out on the first call. On the second call pass the token the first call returned, unchanged.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations flag destructive/openWorld/idempotent, but the description adds the context an agent actually needs: no credits consumed, the site becomes publicly reachable, a token is single-use, publishing is owner-only, and the already-live case short-circuits. This is substantially more than the annotations convey.

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?

The action and its outcome are front-loaded and every sentence carries distinct information (free, token flow, already-live case, unknown-outcome routing, ownership). It is dense and slightly long, but there is no filler.

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?

Given an output schema exists, the description needn't explain return values, and everything else an agent needs for a mutation with an async-ish confirmation step — cost, public exposure, token lifecycle, failure routing, permissions — is covered.

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 parameter documentation is already strong. The description still adds semantics the schema doesn't: the subdomain character rule and 3–63 range, the fallback auto-generated address, and that confirmationToken is only for the second call and cannot be reused.

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 a specific verb and resource — puts a saved site live at name.iter0.app — with the resulting state (anyone can open it). It is clearly distinguishable from create_site, push_site, and unpublish_site, since the description anchors on an existing saved designId and a public address.

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?

Spells out the two-call flow (first call without confirmationToken returns an address and token; second call with the token publishes), the when-not case (already live and up to date needs no token), and an explicit fallback to iter0_publish_status when the outcome is unknown. Little is left to inference.

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.