Skip to main content
Glama

Change a project's publish settings

r3_publish_settings_set
DestructiveIdempotent

Change publish settings of one of the user's own R3 projects in this environment — the app's Deploy → Settings. Only the settings named change (the rest stay as they are). Only when the user asked for it, or approved the text: these settings shape the PUBLIC live page — its title and description in search results and link previews (seoTitle, seoDescription), Works on (keyboard puts a "made for a keyboard" note on phones and a "desktop" badge; touch a "mobile" badge; both, both; untested none — set it only after the user confirmed it or it was tested, never from the code scan alone), how it starts (with a Start button: what runs before the Start button, startButton.before {code, physics}, and whether the project's share picture shows until Start, startButton.poster shareImage), its controls. Invalid values are refused with every problem named, and nothing is saved. The answer names what changed; open live and preview pages are told (a preview reloads, a live page offers a reload). Takes effect without a new release. address changes the public address of a project that is or was live (only when the user asked for it): e.g. "my-game" for r3js.org//my-game; the old address then redirects to the new one, so links already shared keep working. Refused by name when taken, invalid or not live yet (a first go-live chooses it: r3_publish_live slug). Needs the publish:live right. R3 admins only: gallery features, hides or sets the example prompt of a project in the landing gallery (any member's project; send it without settings for a project that is not yours).

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_settings_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoThe new project part of the live address, e.g. "my-game" (letters, numbers and dashes). Only for a project that is or was live; the old address redirects to the new one.
galleryNoR3 admins only: the landing gallery, e.g. {"featured": true} or {"examplePrompt": "…"}.
settingsNoOnly the settings to change, e.g. {"worksOn": "keyboard", "seoDescription": "…"}.
projectIdYesThe project id (r3_project_list).

Output Schema

NameRequiredDescriptionDefault
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.
addressNo
changedYes
galleryNo
projectIdYes
environmentYes
portalSettingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
      +  "description": "The new project part of the live address, e.g. \"my-game\" (letters, numbers and dashes). Only for a project that is or was live; the old address redirects to the new one.",
      +  "maxLength": 120,
      +  "type": "string"
      +}
    • addedOutput schema / properties / address
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "previousSlug": {
      +      "type": "string"
      +    },
      +    "previousUrl": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "slug",
      +    "previousSlug",
      +    "url",
      +    "previousUrl"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "projectId",
      -  "environment",
      -  "changed",
      -  "portalSettings",
      -  "answer"
      -]New value: +[
      +  "projectId",
      +  "environment",
      +  "changed",
      +  "answer"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / settings / properties / startButton / properties / before
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "What runs BEFORE the Start button (startButton and firstGesture modes), e.g. {\"code\": true} so code that builds the scene runs on load; the press starts the rest. Code and physics only: audio and music always wait for the press. Default: nothing.",
      +  "properties": {
      +    "code": {
      +      "type": "boolean"
      +    },
      +    "physics": {
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / settings / properties / startButton / properties / poster
      Added value: +{
      +  "description": "What the page shows before Start: scene (the default) or shareImage (the project's share picture fills the page behind the Start button until Start runs; with no share picture, the scene).",
      +  "enum": [
      +    "scene",
      +    "shareImage"
      +  ],
      +  "type": "string"
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / gallery
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "R3 admins only: the landing gallery, e.g. {\"featured\": true} or {\"examplePrompt\": \"…\"}.",
      +  "properties": {
      +    "examplePrompt": {
      +      "description": "The exact prompt that made this project, shown with a \"Made by R3\" label and a Copy prompt button (up to 500 characters; empty clears it). Only on a project an R3 account owns.",
      +      "maxLength": 500,
      +      "type": "string"
      +    },
      +    "featured": {
      +      "description": "true pins the project to the top of the landing gallery; false unpins it.",
      +      "type": "boolean"
      +    },
      +    "hidden": {
      +      "description": "true keeps the project out of the landing gallery (its live page stays); false shows it again.",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "settings"
      -]New value: +[
      +  "projectId"
      +]
    • addedOutput schema / properties / gallery
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "examplePrompt": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "featured": {
      +      "type": "boolean"
      +    },
      +    "hidden": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "featured",
      +    "hidden",
      +    "examplePrompt"
      +  ],
      +  "type": "object"
      +}
  4. Changed2 schema fields changed
    • changedInput schema / properties / settings / properties / autoStart / description
      Previous value: -"How the live page starts: startButton (a Start button), firstGesture (the first click anywhere), load (on load: physics and code only, no audio)."New value: +"How the live page starts: auto (the default: a Start button only when the project has sound or physics, else it starts on load), startButton (always a Start button), firstGesture (the first click anywhere), load (on load: physics and code only, no audio)."
    • changedInput schema / properties / settings / properties / autoStart / enum
      Previous value: -[
      -  "load",
      -  "startButton",
      -  "firstGesture"
      -]New value: +[
      +  "auto",
      +  "load",
      +  "startButton",
      +  "firstGesture"
      +]
  5. Changed1 schema field changed
    • removedInput schema / properties / settings / properties / publishMode
      Removed value: -{
      -  "description": "What the editor's Save does for a live project: ask, auto (publish) or manual.",
      -  "enum": [
      -    "ask",
      -    "auto",
      -    "manual"
      -  ],
      -  "type": "string"
      -}
  6. 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",
      -  "environment",
      -  "changed",
      -  "portalSettings"
      -]New value: +[
      +  "projectId",
      +  "environment",
      +  "changed",
      +  "portalSettings",
      +  "answer"
      +]
  7. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only give the readOnly/destructive/idempotent/openWorld profile; the description adds substantial behavior beyond that: partial-update semantics ('Only the settings named change'), all-or-nothing validation ('Invalid values are refused with every problem named, and nothing is saved'), the effect on live and preview pages, the fact that changes apply without a new release, old-address redirects, and the publish:live permission requirement.

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

Conciseness3/5

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

The content is front-loaded with the core action, but the prose is a single dense block riddled with nested parentheticals (badges, physics/code lists, gallery asides) that are hard to parse at a glance. Some clauses duplicate the schema descriptions and could be dropped.

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 4-parameter, deeply nested mutation tool with admin-only branches, the description covers mutation semantics, validation, permissions, side effects on live/preview, and address side effects. An output schema exists, so return values need not be spelled out, though it helpfully notes the answer names what changed.

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 the baseline is 3; the description still contributes meaning, notably the redirect consequence of changing `address` and the refusal-by-name condition (taken, invalid, not live yet). Much of the rest (worksOn badge behavior, startButton.before, poster) restates what the nested schema descriptions already say, which caps it below 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?

Opens with a specific verb and resource — 'Change publish settings of one of the user's own R3 projects' — and grounds it in a concrete UI location ('Deploy → Settings'). It is clearly distinguishable from the read counterpart (r3_publish_settings_read) and from the go-live tool (r3_publish_live, whose `slug` it names for a first go-live).

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?

Gives explicit when-to-use conditions ('Only when the user asked for it, or approved the text'), plus a specific gate on `worksOn` ('set it only after the user confirmed it or it was tested, never from the code scan alone') and on `address` ('only when the user asked for it'). It also routes to the alternative for the first-go-live case via r3_publish_live `slug`.

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