Clypmint

Import or export the project

exchange_project

DestructiveIdempotent

Import an After Effects comp, or export Premiere, After Effects, or a portable project (an owned download link). Cost: Free.

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": {
      "direction": "<direction>",
      "format": "<format>",
      "project": "<project>"
    },
    "name": "exchange_project"
  }
}

Input Schema

Name	Required	Description
`assets`	No	Owned media and fonts for this document.
`format`	Yes	after_effects, premiere, or portable.
`project`	Yes	An After Effects comp (JSON or .aep), or a framewright document.
`video_id`	No	Video; the open one if left out.
`direction`	Yes	import an After Effects comp, or export the document.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026
- removedInput schema / properties / assets / items / properties / asset_id / pattern
```
Removed value: -"^src_[A-Za-z0-9_-]{8,96}$"
```
- removedInput schema / properties / assets / items / properties / name / pattern
```
Removed value: -"^[A-Za-z0-9][A-Za-z0-9._-]{0,127}$"
```

Changed3 schema fields changedNov 7, 2026

changedInput schema / properties / direction / description

Previous value: -"import reads an After Effects comp. export writes the document."New value: +"import an After Effects comp, or export the document."

changedInput schema / properties / project / description

Previous value: -"The After Effects comp JSON, a binary .aep, or a framewright document."New value: +"An After Effects comp (JSON or .aep), or a framewright document."

changedInput schema / properties / video_id / description

Previous value: -"The video; the open one when left out."New value: +"Video; the open one if left out."

AddedNov 6, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description adds genuinely useful context beyond annotations: the operation is free of cost, and portable export yields an owned download link. However, the annotations declare destructiveHint=true, and the description never warns that an import can replace or alter the current document, which is the most important behavioral risk for an agent to understand.

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?

A single front-loaded sentence covers the import case first, then the export cases, with the cost note tagged at the end. Efficient overall, though the parenthetical owner-link remark and 'Cost: Free' are slightly tacked-on rather than integrated.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the direction/format enums are covered. But for a destructive, multi-mode tool with three required parameters, the description should say what import does to the existing document and that exports depend on owned assets — both are gaps.

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 every parameter is already documented, and the description merely echoes the format list from the enum. It adds no new meaning about the project payload, the assets pairing, or how video_id selects the target document, so baseline 3 applies.

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?

The description names specific verbs (import/export) and the resource (project), and enumerates the concrete formats exchanged (After Effects comp in; Premiere, After Effects, or portable out), which clearly separates it from the read-only get_project sibling. It stops short of explicitly naming an alternative tool, but the operation and scope are unambiguous.

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?

Usage is implied through the two directions — bring in an AE comp, or send the document out in one of three formats — but there is no explicit when-to-use versus when-not guidance. It also omits the precondition that exported 'owned' assets must already exist, which the assets parameter implies.

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

All Clypmint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?