Change a project's publish settings
r3_publish_settings_setChange 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
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | 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. | |
| gallery | No | R3 admins only: the landing gallery, e.g. {"featured": true} or {"examplePrompt": "…"}. | |
| settings | No | Only the settings to change, e.g. {"worksOn": "keyboard", "seoDescription": "…"}. | |
| projectId | Yes | The project id (r3_project_list). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| answer | Yes | 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. | |
| address | No | ||
| changed | Yes | ||
| gallery | No | ||
| projectId | Yes | ||
| environment | Yes | ||
| portalSettings | No |