Skip to main content
Glama

Preview Product Spot

preview_product_spot
Read-onlyIdempotent

Previews a product-spot assembly from existing project items, revalidating item IDs and reporting host readback before applying to explicit empty tracks.

Instructions

Preview a product-spot assembly from existing project items. The eventual apply is limited to explicit empty tracks, revalidates item IDs, and reports host readback without claiming visual delivery verification.

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": {
      "sequence_id": "<sequence_id>",
      "asset_item_ids": "<asset_item_ids>"
    },
    "name": "preview_product_spot"
  }
}

Input Schema

NameRequiredDescriptionDefault
sequence_idYesExact ID of an existing empty destination sequence. It must be active at apply time.
motion_styleNoScale-motion style for product and brand spots; defaults to alternate.
asset_item_idsYesExact existing project-item node IDs in playback order; external media paths are deliberately not imported by this workflow.
transition_nameNoTransition name; defaults to Cross Dissolve. Use none to disable transitions.
audio_track_indexNoEmpty destination audio track index, default 0.
video_track_indexNoEmpty destination video track index, default 0.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
clip_duration_secondsNoPlanned spacing between asset starts; defaults to 5 seconds for a motion demo and 4 seconds for spots.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.
transition_duration_secondsNoTransition duration, default 0.75 seconds for demos and 0.5 seconds for spots.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so the safety profile is covered. The description adds real value by scoping the eventual apply to explicit empty tracks, promising item-ID revalidation, and explicitly disclaiming visual delivery verification from host readback. However, the second sentence drifts into describing the apply tool rather than this preview, so the added transparency is only partly about this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, purpose front-loaded, no filler. The second sentence is dense but earns most of its words; the only waste is that it describes the apply counterpart's guarantees rather than this tool's own behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and a fully documented ten-parameter nested schema, the description does not need to explain return values or parameters. It correctly frames the preview/apply relationship and the readback-vs-visual-verification caveat; the main omission is the empty-sequence precondition, which only the schema states.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every one of the ten parameters is documented in the schema, including defaults and the nested expected_cep_target guard. The description mentions no parameter at all, so it neither adds nor subtracts; baseline 3 applies when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb ('Preview') plus a specific resource ('a product-spot assembly from existing project items') tells an agent exactly what it produces, and 'from existing project items' scopes the input. It does not name the sibling it complements (preview_brand_spot or apply_spot_workflow_plan), so the differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence about 'the eventual apply' implies this is a preview-before-apply step, so the workflow context is inferable. But no sibling is named, there is no explicit 'use this instead of X' routing, and the precondition that the destination sequence must already be empty appears only in the schema, not the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools