Reference
release_look
Clear the held version so renders follow whatever the designer saved most recently.
What it does
- Writes
- Idempotent
- Account required
The undo for hold_look. Clearing the hold puts the project back on Follow latest, so agents pick up the newest saved version again. A no-op when nothing was held.
You can ask: “Let the Tidebook project follow the latest saved Look again.”
Input
projectstringoptionalat least 1 characterWhich ShotOps project to target: its id (as returned by read_look/save_project), OR its NAME as the user says it — matched exactly, ignoring case and surrounding spaces. Omit = your most recently edited project. A name that matches none or several is refused with the account's projects listed, never resolved by guessing.
Result
okbooleanoptionalprojectobjectoptionalidstringrequirednamestringrequired
heldVersionnulloptionalmessagestringoptional
Example
That request maps to this call:
{
"name": "release_look",
"arguments": {
"project": "Tidebook 2.4 launch"
}
}Confirmation that nothing is held. Safe to call when nothing was held to begin with.
Access and cost
- Needs an account. Not available to an anonymous hosted caller.
- Free. Releasing spends no cloud credits.
When it refuses
- Nothing was held.
- The call succeeds anyway. This is deliberately idempotent — calling it twice is safe.
Where this fits
What the agent is told
The title and description the server publishes on tools/list — this is the copy a model chooses between, reproduced verbatim.
Release the held look
Go back to rendering the newest design: clears a project’s held version (undo hold_look), so agents Follow latest and pick up whatever the designer saved most recently. No-op if nothing was held. No store credential.