Skip to main content
Glama

animate_camera

Create camera animations in Cinema 4D using wiggle, orbit, spline, or linear motion types with customizable positions and keyframes.

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
NameRequiredDescriptionDefault
animation_typeYes
camera_nameNo
positionsNo
framesNo

Implementation Reference

  • The main handler function `animate_camera` that builds the animation command and sends it to Cinema 4D.
    async def animate_camera(
        animation_type: str,
        camera_name: Optional[str] = None,
        positions: Optional[List[List[float]]] = None,
        frames: Optional[List[int]] = None,
        ctx: Context = None,
    ) -> str:
        """
        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
        """
        async with c4d_connection_context() as connection:
            if not connection.connected:
                return "❌ Not connected to Cinema 4D"
    
            # Create command with the animation type
            command = {"command": "animate_camera", "path_type": animation_type}
    
            # Add camera name if provided
            if camera_name:
                command["camera_name"] = camera_name
    
            # Handle positions and frames if provided
            if positions:
                command["positions"] = positions
    
                # Generate frames if not provided (starting at 0 with 15 frame intervals)
                if not frames:
                    frames = [i * 15 for i in range(len(positions))]
    
                command["frames"] = frames
    
            if animation_type == "orbit":
                # For orbit animations, we need to generate positions in a circle
                # if none are provided
                if not positions:
                    # Create a set of default positions for an orbit animation
                    radius = 200  # Default orbit radius
                    height = 100  # Default height
                    points = 12  # Number of points around the circle
    
                    orbit_positions = []
                    orbit_frames = []
    
                    # Create positions in a circle
                    for i in range(points):
                        angle = (i / points) * 2 * 3.14159  # Convert to radians
                        x = radius * math.cos(angle)
                        z = radius * math.sin(angle)
                        y = height
                        orbit_positions.append([x, y, z])
                        orbit_frames.append(i * 10)  # 10 frames between positions
    
                    command["positions"] = orbit_positions
                    command["frames"] = orbit_frames
    
            # Send the command to Cinema 4D
            response = send_to_c4d(connection, command)
    
            return format_c4d_response(response, "animate_camera")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates an animation but doesn't explain what that entails—whether it modifies existing scenes, requires specific permissions, has side effects, or what the expected outcome looks like. This leaves significant gaps for an AI agent to understand the tool's behavior.

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 description is front-loaded with the core purpose, followed by a structured list of parameters. It's efficient with minimal waste, though the parameter explanations could be slightly more detailed without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a 4-parameter tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like what the tool returns, error conditions, or how it integrates with sibling tools (e.g., 'create_camera'). This makes it inadequate for an AI agent to use the tool confidently in a 3D animation workflow.

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

Parameters3/5

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

The schema description coverage is 0%, so the description must compensate. It lists all parameters and provides basic semantics (e.g., 'animation_type' options, 'positions' as [x,y,z] lists), adding value beyond the bare schema. However, it doesn't explain how parameters interact (e.g., if 'positions' and 'frames' must match in length) or provide examples, leaving some ambiguity.

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 clearly states the verb ('Create') and resource ('camera animation'), making the purpose evident. However, it doesn't differentiate this tool from sibling tools like 'set_keyframe' or 'create_camera', which might have overlapping functionality in a 3D animation context.

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?

No guidance is provided on when to use this tool versus alternatives like 'set_keyframe' or 'create_camera'. The description lacks context about prerequisites, such as whether a camera must exist first, or when different animation types are appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ttiimmaacc/cinema4d-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server