list_versionsList the versions of a video, newest last, and which one is live. Use with restore_version to undo. Cost: Free: no credits.
| Name | Required | Description | Default |
|---|---|---|---|
| video_id | Yes | The video id from list_videos. |
| 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 | ||
| versions | No | ||
| video_id | No | ||
| available | No | ||
| import_id | No | ||
| output_id | No | ||
| studio_url | No | ||
| version_id | No |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Clypmint list_versions 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"
+ ]
+ },
+ "version_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "versions": {
+ "items": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "video_id": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: result ordering (newest last), inclusion of the live-version indicator, and the free/no-credit cost. It doesn't discuss pagination, though an output schema exists to cover the shape.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short clauses, front-loaded with purpose and ordering, then workflow pairing, then cost. No filler sentences; each clause carries distinct information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter read-only list tool with an output schema, the description covers what an agent needs: what it returns (versions, newest last, live flag), how it relates to restore_version, and that it costs nothing. Nothing material is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single required video_id is documented there ('The video id from list_videos'). The description adds no syntax or format detail beyond the schema, so the baseline 3 for schema-carried parameters is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (versions of a video), plus distinguishing output facts — ordering (newest last) and which version is live. It also names the sibling it pairs with (restore_version), so an agent can place it without reading the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly ties the tool to restore_version for undoing changes, giving a clear workflow context. It stops short of stating when-not-to-use or naming other alternatives, but the intended use is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.