asset_finalize

Complete an upload after the bytes have been PUT, validate the file, and add the Asset to your library — optionally registering it in the same call.

Completes an upload after the bytes have been PUT to the URL from asset_create_upload, and adds the Asset to your library. The file is validated here — nothing about it is known until it lands — so a wrong type or an oversized file is rejected at this step.

Input

Output

{ asset, registration? }:

• asset — the finalized Asset (now status: 'ready'), shaped like an asset_list row.
• registration — present only when advertiser_id was given: the outcome of the inline registration.

Example

“Finalize that upload and register it to the Acme account.”

Claude calls asset_finalize({ asset_id: 'ast_…', advertiser_id: 'acc_…' }), then polls asset_get until the Registration is ready.

Errors

Finalizing refuses a file it can’t turn into a usable Asset:

• not_uploaded — the bytes haven’t arrived. PUT them to the uploadUrl first, then call again.
• too_large — larger than the provider accepts. The file is discarded; upload a smaller version.
• unsupported_type — not usable in ads. Discarded; use JPEG, PNG, WebP, GIF, or MP4.
• type_mismatch — the bytes are a different type from the Content-Type they were uploaded with. Discarded; upload again with the real type.
• unreadable — the bytes are no accepted type, or the file ends before its header does. Discarded; upload an intact file of an accepted type.
• not_found — no such Asset in this organization.
• 401 or 403 — see Errors, which every tool shares. This one needs asset:write.

Reference

Complete an upload after the bytes have been PUT, and add the Asset to the library.

The file is checked here rather than earlier — nothing about it is known until it arrives — so this is where a wrong type or an oversized file is rejected.

Input

Failure codes

A failed call has isError set, and structuredContent.error holds one of these codes. Errors describes the shape of a failed call.

• not_found
• not_uploaded
• too_large
• type_mismatch
• unreadable
• unsupported_type
• forbidden
• invalid_request
• internal_error

Scope

The token must hold asset:write. Auth & scopes lists each scope.

Annotations

A client reads these hints. A hint that the tool does not declare has the default value of the MCP specification.

• Writes. The tool can change data.
• Destructive. The tool can make a change that you cannot undo. A client can ask you to confirm before it calls the tool.
• Idempotent. A second call with the same arguments changes nothing more.
• Closed world. The tool reads and writes the data of AdCrunch only.