Skip to main content
Glama

Preview Send Clip To After Effects

preview_send_clip_to_after_effects
Read-onlyIdempotent

Previews sending a Premiere video clip to After Effects, checks media, sequence and AE project, flags effects that won’t carry over, and returns a token for applying the swap.

Instructions

Preview sending one video timeline clip to After Effects, like Premiere's Replace with After Effects Composition. Reads the clip, its source media and the sequence, and the open saved AE project. Refuses speed-changed, reversed, offline or non-file clips. Lists effects and Motion/Opacity changes on the clip that the swap would not carry over. Changes nothing; returns a ten-minute token for apply_send_clip_to_after_effects.

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": {
      "node_id": "<node_id>",
      "ae_project_path": "<ae_project_path>",
      "approved_workspace_path": "<approved_workspace_path>"
    },
    "name": "preview_send_clip_to_after_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYesNode ID of the video clip on the active sequence.
comp_nameNoOptional composition name (default: '<clip name> Linked Comp'); a number is added if it is taken.
target_bin_idNoOptional node ID of the Premiere bin for the linked comp (default: project root).
ae_project_pathYesThe After Effects project open in AE, saved to disk. The comp is added to it and it is saved.
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
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.
approved_workspace_pathYesExisting absolute folder that must contain ae_project_path.

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

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the readOnly/destructive/idempotent annotations: what it reads (clip, source media, sequence, open saved AE project), what it refuses, that it reports effects and Motion/Opacity changes the swap would drop, that it mutates nothing, and that the returned token expires in ten minutes.

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

Conciseness5/5

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

Five dense sentences, front-loaded with purpose, then reads/refusals, then the non-carried-over effects caveat, then the no-change/token outcome. No filler; each sentence carries distinct information.

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?

For a read-only preview with an output schema and rich annotations, the description covers the essential behavior: preconditions, side-effect-free semantics, and the token handoff. It leaves the idempotency and expected-CEP-guard behavior entirely to the schema, which is a minor omission given the tool's nested-object complexity.

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 coverage is 100%, so all 8 parameters, including the nested expected_cep_target guard, are already documented in the schema. The description only echoes the requirement that the AE project be open and saved (ae_project_path); it does not add semantics for comp_name, target_bin_id, idempotency_key or the guard fields, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb (preview) and resource (sending one video timeline clip to After Effects), anchors it with a concrete analogy (Premiere's Replace with After Effects Composition), and distinguishes it from the sibling apply_send_clip_to_after_effects by naming it as the follow-up.

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

Usage Guidelines4/5

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

Makes the when clear: this is the dry-run that returns a token for apply_send_clip_to_after_effects, so the agent knows to preview first. It also gives concrete preconditions (refuses speed-changed, reversed, offline or non-file clips) but does not spell out when the apply step should be skipped or what to do after a refusal.

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