hold_look

What it does

• Writes
• Idempotent
• Account required

Freeze which design gets delivered. Pinning a version makes it the project’s default, so a designer can go on saving newer versions without changing what agents render. The version has to exist already — read_look lists them. release_look goes back to following the latest.

You can ask: “Keep the Tidebook project on the Look version the team approved.”

Input

• projectstringoptionalat least 1 character

  Which 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.

• versionintegerrequiredmin 1

  The saved look version to HOLD as the one agents render by default (see read_look versions).

Result

• okbooleanoptional

• projectobjectoptional

  • idstringrequired

  • namestringrequired

• heldVersionnumberoptional

• messagestringoptional

Example

That request maps to this call:

{
  "name": "hold_look",
  "arguments": {
    "project": "Tidebook 2.4 launch",
    "version": 3
  }
}

Confirmation of the held version. Calling it again with the same version changes nothing.

Access and cost

• Needs an account. Not available to an anonymous hosted caller.
• Free. Holding spends no cloud credits.

When it refuses

The version does not exist.

Read the version list first. Holding cannot create a version.

A render still comes back looking like something else.

Holding only affects renders that ask for the saved look. Pass useSavedLook: true, or an inline look wins over the held one.

Where this fits

• Hold and Follow latest, end to end

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.