Clypmint

Browse editing styles

browse_styles

Read-onlyIdempotent

Show ready styles/copies with content format (faceless/motion/talking), frame formats, jobs, best_for, actual inputs and saved style_version when available. Motion is faceless type/music with inputs.voice:none by default; an explicit voiceover request overrides that default while keeping the visual style and aligns visuals to the recorded speech. Narrated faceless styles use inputs.voice:narrator. Also returns all 21 narrator descriptions, accent/tags and public audition URLs; use catalog names in create_video voice. Recommend suitable returned styles, never invent private IDs. Listen/show auditions before selecting an undecided voice.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 14, 2026
- addedOutput schema / properties / styles / items / properties / preview_credits_url
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / styles / items / properties / preview_shape
```
Added value: +{
+  "enum": [
+    "9:16",
+    "16:9"
+  ],
+  "type": "string"
+}
```

Changed4 schema fields changedOct 13, 2026

addedOutput schema / properties / narrators

Added value: +{
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / styles / items / properties / best_for / type
```
Previous value: -"array"New value: +[
+  "array",
+  "string",
+  "null"
+]
```

changedOutput schema / properties / styles / items / properties / format / enum

Previous value: -[
-  "talking",
-  "faceless",
-  "motion"
-]New value: +[
+  "talking",
+  "faceless",
+  "motion",
+  null
+]

changedOutput schema / properties / styles / items / properties / format / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 13, 2026

addedOutput schema / properties / styles / items / properties

Added value: +{
+  "best_for": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "format": {
+    "enum": [
+      "talking",
+      "faceless",
+      "motion"
+    ],
+    "type": "string"
+  },
+  "id": {
+    "type": "string"
+  },
+  "inputs": {
+    "additionalProperties": true,
+    "properties": {
+      "footage": {
+        "enum": [
+          "required",
+          "optional",
+          "none"
+        ],
+        "type": "string"
+      },
+      "music": {
+        "enum": [
+          "like-reference",
+          "their-song",
+          "none"
+        ],
+        "type": "string"
+      },
+      "narrator": {
+        "type": "string"
+      },
+      "pictures": {
+        "items": {
+          "enum": [
+            "theirs",
+            "web",
+            "stock"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "voice": {
+        "enum": [
+          "theirs",
+          "narrator",
+          "none"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "preview_label": {
+    "type": "string"
+  },
+  "preview_source": {
+    "enum": [
+      "reference",
+      "native",
+      "sample"
+    ],
+    "type": "string"
+  }
+}

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Clypmint browse_styles result. Error results carry error; successful requests expose the identifiers and state available for the next step. Signed media stays in private metadata.",
+  "properties": {
+    "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"
+    },
+    "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"
+      ]
+    },
+    "styles": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "version_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "video_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), yet the description adds non-obvious behavioral semantics: motion defaults to inputs.voice:none, an explicit voiceover overrides that while preserving the visual style and aligning visuals to speech, and narrated faceless styles use inputs.voice:narrator. That is meaningful default/override disclosure beyond the structured annotations, though return-format expectations remain thin.

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 purpose is front-loaded in the first clause, and the dense semicolon-separated clauses each carry content (format types, voice defaults, narrator catalog, audition guidance). It is information-heavy for a simple listing tool, but no sentence is pure filler.

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 no-parameter read tool with an output schema, the description is complete enough: it explains what is returned in categorical terms, the voice/default behavior, and how to act on auditions. Some enumerated return fields partially duplicate the output schema, but the behavioral rules (motion voiceover override, narrator voice) are what the schema would not convey.

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?

The tool takes zero parameters (additionalProperties: false), so there are no parameter semantics to explain; baseline 4 applies. The description instead documents referenced fields of returned styles (voice, style_version), which is relevant context rather than parameter guidance.

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 opens with a specific verb+resource ('Show ready styles/copies') and enumerates what the listing contains: content format, frame formats, jobs, best_for, inputs, style_version, plus narrator descriptions and audition URLs. It is clearly a read/discovery tool, but it never names or distinguishes itself from siblings like adjust_style, copy_style, or apply_edits, so an agent must infer the boundary.

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?

It offers workflow guidance ('Recommend suitable returned styles, never invent private IDs', 'Listen/show auditions before selecting an undecided voice') that shapes downstream behavior, which is genuinely useful. However, it gives no explicit when-to-use/when-not-to-use framing against the sibling style tools, so usage is only implied.

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?