R3

Create a preview link

r3_preview_create

DestructiveIdempotent

Create a shareable preview link for a saved R3 project, so a person can open it in a browser and see it running. The link is valid for 7 days and does NOT make the project public; making a new one is free. It is how the user sees what you built. Takes the projectId returned by r3_project_create. When an R3 tab has the project open, the project's picture (its card and the link's image) is refreshed from that tab; when none has, the picture refreshes the next time the project is opened in R3.

Input Schema

Name	Required	Description	Default
`projectId`	Yes	The project id, as returned by r3_project_create.

Output Schema

Name	Required	Description
`slug`	Yes
`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.
`projectId`	Yes
`previewUrl`	Yes
`environment`	Yes
`cameraControls`	Yes
`expiresInHours`	Yes
`pictureOutdated`	Yes
`pictureRefreshed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedOutput schema / properties / cameraControls

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "projectId",
-  "previewUrl",
-  "slug",
-  "expiresInHours",
-  "environment",
-  "pictureRefreshed",
-  "pictureOutdated",
-  "answer"
-]New value: +[
+  "projectId",
+  "previewUrl",
+  "slug",
+  "expiresInHours",
+  "environment",
+  "pictureRefreshed",
+  "pictureOutdated",
+  "cameraControls",
+  "answer"
+]

Changed2 schema fields changedOct 23, 2026

addedOutput schema / properties / pictureOutdated
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "projectId",
-  "previewUrl",
-  "slug",
-  "expiresInHours",
-  "environment",
-  "pictureRefreshed",
-  "answer"
-]New value: +[
+  "projectId",
+  "previewUrl",
+  "slug",
+  "expiresInHours",
+  "environment",
+  "pictureRefreshed",
+  "pictureOutdated",
+  "answer"
+]

Changed2 schema fields changedOct 16, 2026

addedOutput schema / properties / pictureRefreshed
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "projectId",
-  "previewUrl",
-  "slug",
-  "expiresInHours",
-  "environment",
-  "answer"
-]New value: +[
+  "projectId",
+  "previewUrl",
+  "slug",
+  "expiresInHours",
+  "environment",
+  "pictureRefreshed",
+  "answer"
+]

Changed2 schema fields changedOct 15, 2026

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",
-  "previewUrl",
-  "slug",
-  "expiresInHours",
-  "environment"
-]New value: +[
+  "projectId",
+  "previewUrl",
+  "slug",
+  "expiresInHours",
+  "environment",
+  "answer"
+]

First observedOct 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover mutation/open-world/idempotent/destructive traits, and the description adds useful non-obvious behavior: 7-day validity, not public, free to recreate, and preview-image refresh behavior depending on whether an R3 tab has the project open. It does not explain why destructiveHint=true applies, but it does not contradict that annotation.

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 purpose is front-loaded and the key constraints (7 days, not public, free) are stated early. The final sentence about preview-image refresh is detailed but still adds useful nuance rather than padding.

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

Completeness4/5

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

With an output schema present and a single fully documented parameter, the description supplies enough context to call the tool correctly, including expiry and privacy behavior. A brief note clarifying the destructive annotation would make it fully complete.

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 the projectId parameter is already fully documented in the input schema. The description only repeats that it comes from r3_project_create and adds no extra syntax or format guidance.

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: create a shareable preview link for a saved R3 project so it can be opened in a browser. This clearly distinguishes it from siblings like r3_preview_remove and r3_publish_live.

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?

Explains the practical use case ("how the user sees what you built") and implicitly distinguishes it from publishing by noting it does NOT make the project public. It stops short of explicitly naming alternatives such as r3_publish_live or r3_preview_remove.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All R3 tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?