Get Preview URL
get_preview_urlShow the user a live preview card and return the preview link. On an EXISTING project this is typically called EARLY, before the first change, so the user watches edits live from the start; the result is informational and a working session normally continues past it. It is not needed right after create_project, whose result already includes the same card. The preview URL carries an access token in its query string and only works shared EXACTLY as returned (no Floot login, view-only — which is also what lets it open on a phone); it live-updates as you edit, so it also suits an in-app browser tab if your client has one. The result additionally includes the sandbox API base for your own headless /_api/* testing — the frontend does not render there and it is not a user-facing URL; the preview link is the one meant for the user. Floot hosts the app: publish_app publishes it to production. To send the user straight to one view (a page, a component's examples, a page's staged screens, a design canvas or one of its frames, a page's link preview card), pass targetType with path or name, as navigate_preview takes them: the link then opens on that view, with or without a Floot window open.
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": "get_preview_url"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | The other targetTypes: the item name as list_files shows it, with "#<screen>" for page examples or "#<section, frame or bookmark id>" for a design ("CheckoutExplorations#payment"). | |
| path | No | targetType "page" or "link-preview": a path from "/", query and hash allowed. | |
| projectId | Yes | ||
| targetType | No | Optional: the view the link opens on, as navigate_preview's targetType. Omit for the plain preview. |