Skip to main content
Glama

Publish a project live

r3_publish_live
Destructive

Publish an R3 project live: makes a RELEASE (a frozen copy) of the project as it is now and makes it the one its public live URL shows, for anyone. Only when the user asked for it. Changing the project does NOT change the live site; r3_publish_live does: on a project that is already live this is a publish update (a new release replaces the live one), and the answer names the release number and what changed since the previous live release. note (optional, up to 500 characters) is stored with the release. slug (optional, the first time a project goes live) is the project part of its public address (e.g. "my-game" for …//my-game: letters, numbers and dashes); without it R3 uses a free address (the project's name when free) and the answer says which. Once a project has been live its address never changes. Going live the FIRST time uses one of the live-project slots of the project owner's plan (an update uses none); going live needs a plan. When there is no plan or no room, nothing is published and the answer says how many live projects the plan allows, how many are used and where the user picks a plan. It publishes every change kept so far (yours and the user's: there is nothing to save first). r3_release_list shows the releases, r3_release_rollback makes an older one live again. Needs the publish:live right.

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": {
      "projectId": "<projectId>"
    },
    "name": "r3_publish_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional: what this release is, in a few words (up to 500 characters), e.g. "new cue and rules".
slugNoOptional, first go-live only: the project part of the public address, e.g. "my-game" (letters, numbers and dashes). Without it R3 uses a free address and says which. A project that has been live keeps its address here (a different slug is refused): r3_publish_settings_set `address` changes it.
projectIdYesThe project id (r3_project_list / r3_project_create).

Output Schema

NameRequiredDescriptionDefault
liveYes
noteYes
slugYes
answerYesThis answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.
changesYes
liveUrlYes
embedCodeYes
projectIdYes
environmentYes
firstGoLiveYes
addressChosenYes
releaseNumberYes
previousNumberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Optional, first go-live only: the project part of the public address, e.g. \"my-game\" (letters, numbers and dashes). Without it R3 uses a free address and says which. A project that has been live keeps its address: a different slug is refused."New value: +"Optional, first go-live only: the project part of the public address, e.g. \"my-game\" (letters, numbers and dashes). Without it R3 uses a free address and says which. A project that has been live keeps its address here (a different slug is refused): r3_publish_settings_set `address` changes it."
  2. Changed3 schema fields changed
    • addedInput schema / properties / slug
      Added value: +{
      +  "description": "Optional, first go-live only: the project part of the public address, e.g. \"my-game\" (letters, numbers and dashes). Without it R3 uses a free address and says which. A project that has been live keeps its address: a different slug is refused.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
    • addedOutput schema / properties / addressChosen
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "pinned",
      +        "requested",
      +        "suggested"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "liveUrl",
      -  "slug",
      -  "live",
      -  "environment",
      -  "releaseNumber",
      -  "previousNumber",
      -  "firstGoLive",
      -  "note",
      -  "changes",
      -  "embedCode",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "liveUrl",
      +  "slug",
      +  "live",
      +  "environment",
      +  "releaseNumber",
      +  "previousNumber",
      +  "firstGoLive",
      +  "addressChosen",
      +  "note",
      +  "changes",
      +  "embedCode",
      +  "answer"
      +]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / embedCode
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "liveUrl",
      -  "slug",
      -  "live",
      -  "environment",
      -  "releaseNumber",
      -  "previousNumber",
      -  "firstGoLive",
      -  "note",
      -  "changes",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "liveUrl",
      +  "slug",
      +  "live",
      +  "environment",
      +  "releaseNumber",
      +  "previousNumber",
      +  "firstGoLive",
      +  "note",
      +  "changes",
      +  "embedCode",
      +  "answer"
      +]
  4. Changed2 schema fields changed
    • addedOutput schema / properties / answer
      Added value: +{
      +  "description": "This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "liveUrl",
      -  "slug",
      -  "live",
      -  "environment",
      -  "releaseNumber",
      -  "previousNumber",
      -  "firstGoLive",
      -  "note",
      -  "changes"
      -]New value: +[
      +  "projectId",
      +  "liveUrl",
      +  "slug",
      +  "live",
      +  "environment",
      +  "releaseNumber",
      +  "previousNumber",
      +  "firstGoLive",
      +  "note",
      +  "changes",
      +  "answer"
      +]
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

The description clarifies specific behaviors not covered by annotations, such as publishing a 'frozen copy' of the project and detailing how the public address never changes once live.

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?

While detailed, the length is justified by the complex nature of the tool (licensing, address stability, release mechanics); the structure moves logically from general purpose to specific constraints.

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 the complexity of live project hosting, the definition covers all necessary operational knowledge, including resource usage limits and release persistence.

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?

Even with 100% schema coverage, the description adds critical context, explaining that `slug` is only used on first go-live and that address changes require a separate tool, `r3_publish_settings_set`.

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 description clearly defines the function (publishing a project live) and distinguishes it from setting up release metadata, explicitly mentioning related tools like `r3_release_list` and `r3_release_rollback`.

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?

It provides extensive conditional guidance, explaining the difference between a first-time go-live (needs slug) and subsequent updates (replaces live release), and details failure modes based on plan limits.

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