delete_assets

What it does

• Writes
• Destructive
• Idempotent
• Account required

Cleanup after delivery, offered rather than performed. It accepts opaque asset ids, refuses live Project, operation, share and preview dependencies, and permanently removes only unreferenced owned bytes. Missing or already-deleted ids converge without error; foreign ids reveal nothing. Nothing has to be cleaned up: an asset left alone expires on its own, so offer only assets a live resource no longer depends on.

You can ask: “Delete the temporary assets this completed run created.”

Annotated destructive and idempotent: the same refs deleted twice leave the same state, but the first call cannot be undone.

Input

• assetIdsarrayoptionalat most 50 items

  Asset ids from earlier results.

  each item

  string

• refsarrayoptionalat most 50 items

  Refs from earlier results, when no asset id is at hand. Deletion is irreversible.

  each item

  string

Result

• okbooleanrequired

• deletedCountnumberoptional

• deletedAssetIdsarrayoptional

  each item

  string

• messagestringoptional

Example

That request maps to this call:

{
  "name": "delete_assets",
  "arguments": {
    "assetIds": [
      "11111111-1111-4111-8111-111111111111"
    ]
  }
}

The opaque ids removed; live dependencies are returned as a typed asset_in_use refusal.

Access and cost

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

When it refuses

Deletion is refused because a Project, operation, share or preview still depends on an asset.

Deletion is refused with the dependency kind and any caller-visible owned resource id.

An asset id is missing or belongs to somebody else.

It is reported only as not found. No foreign asset or dependency fact is disclosed.

Where this fits

• Cleaning up what a CI run created

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.