Clypmint

Import a shared asset

import_asset

Idempotent

Import one image or song up to 32 MiB for a video: a file attached in ChatGPT (file), or a public https link to the file (url) from Claude or any host that cannot attach files. logo: true marks the image as the brand’s logo. Returns an asset_staging_key for create_video’s asset_staging_keys (or music_staging_key for a song), usable for seven days. Repeating the same operation_id and file returns the original receipt. Does not import video footage (edit_video does) or read the host’s wider library. No link and no attachment? The account owner can add the logo once on the Brand page (no website needed): https://clypmint.com/studio/brand.

Input Schema

Name	Required	Description
`url`	No	A public https link to the image (PNG, JPEG, WebP, GIF) or song (MP3, WAV, M4A), up to 32 MiB. Use it from Claude or any host that cannot attach a file: the direct link to the file itself, not a page that shows it.
`file`	No	A file attached in ChatGPT. Hosts that cannot attach files send url instead.
`logo`	No	true when the image is the brand's logo: the video uses it as the brand's mark.
`file_name`	No	A name for the file.
`operation_id`	Yes

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
`mime_type`	No
`output_id`	No
`studio_url`	No
`version_id`	No
`asset_staging_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 14, 2026

addedInput schema / properties / file / description

Added value: +"A file attached in ChatGPT. Hosts that cannot attach files send url instead."

addedInput schema / properties / file_name

Added value: +{
+  "description": "A name for the file.",
+  "maxLength": 120,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / logo

Added value: +{
+  "description": "true when the image is the brand's logo: the video uses it as the brand's mark.",
+  "type": "boolean"
+}

addedInput schema / properties / url

Added value: +{
+  "description": "A public https link to the image (PNG, JPEG, WebP, GIF) or song (MP3, WAV, M4A), up to 32 MiB. Use it from Claude or any host that cannot attach a file: the direct link to the file itself, not a page that shows it.",
+  "format": "uri",
+  "maxLength": 2000,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "operation_id",
-  "file"
-]New value: +[
+  "operation_id"
+]

Changed1 schema field changedOct 13, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Clypmint import_asset result. Error results carry error; successful requests expose the identifiers and state available for the next step. Signed media stays in private metadata.",
+  "properties": {
+    "asset_staging_key": {
+      "type": "string"
+    },
+    "available": {
+      "type": "boolean"
+    },
+    "code": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "cost": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "dry_run": {
+      "type": "boolean"
+    },
+    "error": {
+      "type": "string"
+    },
+    "import_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    },
+    "output_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "integer",
+        "null"
+      ]
+    },
+    "studio_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "style_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "version_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "video_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedOct 10, 2026

changedInput schema / properties / file / required

Previous value: -[
-  "download_url",
-  "file_id",
-  "mime_type",
-  "file_name"
-]New value: +[
+  "download_url",
+  "file_id"
+]

AddedOct 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the 32 MiB cap, the seven-day lifetime of the staging key, and the idempotency mechanism (same operation_id and file returns the original receipt). Annotations already flag idempotentHint and openWorldHint, so the added expiry and size limits are the real value; rate limits and permission requirements go unmentioned.

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?

Front-loaded with the core action and size limit, then the input-path branching. Slightly dense in a single paragraph, and the closing Brand-page URL is a mild tangent, though it serves a real dead-end case.

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?

Covers the input modes, the size ceiling, logo semantics, the return value's downstream use (asset_staging_keys on create_video), and its expiry. With an output schema present and 80% param coverage, nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

With 80% schema coverage the baseline is 3, but the description adds genuine meaning: it explains when to prefer url over file, that logo:true designates the brand mark, and what operation_id buys (idempotent replay). Only the file_name parameter gets no added explanation.

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 (import), the exact resource (one image or song up to 32 MiB), and immediately names what it is not: "Does not import video footage (edit_video does)." An agent can distinguish it from list_assets and edit_video without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes between the two input paths: file for attachments in ChatGPT, url "from Claude or any host that cannot attach files." It names the exclusion (no video footage; edit_video does that) and gives a fallback for the no-link no-attachment case via the Brand page.

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?