Cinema4D MCP

Overview Schema Source Related Servers Discussions Admin

animate_camera

Create camera animations in Cinema 4D by choosing wiggle, orbit, spline, or linear motion. Define keyframe positions and frames for custom camera movement.

Instructions

Create a camera animation.

Args:
    animation_type: Type of animation (wiggle, orbit, spline, linear)
    camera_name: Optional name of camera to animate
    positions: Optional list of [x,y,z] camera positions for keyframes
    frames: Optional list of frame numbers for keyframes

Input Schema

TableJSON Schema

Name	Required	Description	Default
`frames`	No
`positions`	No
`camera_name`	No
`animation_type`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Sep 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The description does not disclose whether the animation replaces an existing animation, whether it mutates the scene permanently, or what happens when camera_name is omitted. With no annotations to supply the safety profile, the description carries the burden alone and only states the basic creation intent.

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 compact, opens with a clear verb phrase, and uses an argument list that scans quickly. Nothing is redundant and every line earns its place.

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?

It gives enough parameter-level semantics for a basic call, and an output schema presumably covers the return value. It is still thin on behavioral context such as defaults, ownership of the animation, and interaction with other scene objects, so it is only minimally acceptable for an AI agent.

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 schema presumably only lists unnamed parameters, while the description adds practical meaning: animation_type accepts wiggle/orbit/linear, positions are [x,y,z] keyframe values, and frames are frame numbers. This is genuine value beyond the schema, though alignment between positions and frames could be clarified further.

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 phrase 'Create a camera animation' identifies a specific verb and resource, and the parameter list clarifies that it handles wiggle, orbit, linear, and spline animations. It does not explicitly distinguish itself from the sibling set_keyframe, but its scope is reasonably clear.

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

Usage Guidelines2/5

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

There is no guidance about when to choose this tool over alternatives such as set_keyframe or create_camera, nor about prerequisites like whether a camera must already exist. The description only states what the parameters are, not the intended workflow.

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