Clip Studio MCP

list_character_film_catalog

Read-only

List Character Films narrators, looks, and lengths. Same catalog as /character-films. Each narrator includes voiceName (the narrator’s fixed voice). Does not render or charge. Subtitles are burned automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`looks`	Yes	Illustration looks (id, name, tagline) for reference. Each narrator has a fixed lookId; there is no separate look choice.
`lengths`	No	Full film lengths in seconds (30, 60, 120, 180).
`narrators`	Yes	Narrators (id, name, tagline, archetype, voiceName, lookId). Pick narratorId from this list; the narrator brings its own look and voice.
`freeOpeningMaxSeconds`	No	Maximum length of the free first opening, in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026

changedOutput schema / properties / looks / description

Previous value: -"Illustration looks (id, name, tagline). Pick lookId from this list."New value: +"Illustration looks (id, name, tagline) for reference. Each narrator has a fixed lookId; there is no separate look choice."

changedOutput schema / properties / narrators / description

Previous value: -"Narrators (id, name, tagline, archetype). Pick narratorId from this list."New value: +"Narrators (id, name, tagline, archetype, voiceName, lookId). Pick narratorId from this list; the narrator brings its own look and voice."

Changed2 schema fields changedSep 26, 2026

removedOutput schema / properties / captionStyles

Removed value: -{
-  "description": "Story caption looks Character Films can burn in.",
-  "items": {
-    "description": "Caption look id such as spotlight or off.",
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / defaultCaptionStyle

Removed value: -{
-  "description": "Default caption look (spotlight).",
-  "type": "string"
-}

AddedSep 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds behavior beyond the readOnlyHint annotation by stating it 'does not render or charge' and that subtitles are burned automatically. This informs the agent of side-effect-free operation and a property of the returned data, which is useful and consistent with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences with no fluff. The primary purpose is front-loaded in the first sentence, additional context follows, and every sentence contributes meaningful information without redundancy.

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 parameterless list tool with an output schema present and annotations covering safety, the description adequately covers behavior (no render/charge), output content (narrators, looks, lengths, voiceName), and a notable data property (subtitles). It does not specify pagination or sorting, but these are likely detailed in the output schema, making this sufficient.

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 input schema has zero parameters, so there is no parameter information to add. The description correctly omits any param explanations, and the baseline score of 4 applies since the schema fully covers an empty parameter set.

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 clearly states the tool lists Character Films with specific attributes (narrators, looks, lengths) and references the canonical catalog endpoint. This precise resource and verb set it apart from other list_* tools like list_audio_lab_voices or list_storyboard_themes, so an agent knows exactly what it retrieves.

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?

The description provides clear context: it is the list operation for the character film catalog and mentions the equivalent endpoint. It does not explicitly exclude alternatives or state when not to use it, but given the tool's name and the limited sibling set for this resource, the intended usage is unambiguous. A short note about using get_character_film for single-film details would push it to 5.

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

All Clip Studio MCP 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?