Skip to main content
Glama

Apply Send Clip To After Effects

apply_send_clip_to_after_effects

Sends a previewed Premiere clip to After Effects, builds a comp with the exact source range, saves and imports it over Dynamic Link, then replaces the timeline clip while keeping linked audio.

Instructions

Send the previewed clip to After Effects: recheck the clip, add a comp with its exact source range (footage layer audio off) to the open AE project and save it, import the comp into Premiere over Dynamic Link, then replace the clip with it at the same timeline span. The original's linked audio stays. Requires confirmation; the token is single-use. A failure after the AE save leaves the comp in AE and reports where it stopped.

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": {
      "preview_token": "<preview_token>",
      "confirm_send": "<confirm_send>"
    },
    "name": "apply_send_clip_to_after_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_sendYesMust be true after reviewing the plan and any effects that will not carry over.
preview_tokenYesOne-time token from preview_send_clip_to_after_effects.
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.

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?

Beyond annotations it discloses the concrete mutation (the clip is replaced at the same timeline span, original's linked audio retained), the auth/confirmation model (single-use token, explicit confirm flag), and partial-failure semantics ("A failure after the AE save leaves the comp in AE and reports where it stopped"). This is exactly the context annotations cannot express.

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?

The action is front-loaded and every sentence carries information about execution order or failure behavior. The sentences are long and multi-clause (the first packs five steps), so a numbered breakdown would read faster, but there is no filler.

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

Completeness5/5

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

For a destructive-ish, multi-application mutation with five parameters, the definition covers preconditions, side effects, side-effect persistence on failure, and what survives the edit. Output shape is covered by the output schema and parameter details by the schema, so nothing an agent needs before calling is missing.

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%, so the parameters are already fully documented in structured form; the description only reinforces that the token is single-use and confirmation is required. It adds nothing about expected_cep_target or expected_project_path guards, which are explained in the schema instead, 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?

The description opens with a specific verb and destination ("Send the previewed clip to After Effects") and then enumerates the exact sequence: recheck clip, add comp at exact source range, save AE project, import via Dynamic Link, replace clip at same span. This makes it trivially distinguishable from the sibling preview_send_clip_to_after_effects, which it implicitly references via the token.

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?

It states the precondition clearly (a one-time preview_token plus confirm_send=true after reviewing the plan), which defines when this tool is callable vs. the preview tool. It does not explicitly say "call preview_send_clip_to_after_effects first" or name an alternative for a dry-run, so the sequencing is inferable rather than spelled out.

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