Skip to main content
Glama

Create C4D Entity

create_entity

Create Cinema 4D objects, tags, materials, shaders, or video_post effects with parent linking, parameters, positions, and container slot assignment in a single call. Returns entity handle for further operations.

Instructions

Unified constructor for object / tag / material / shader / video_post. Handles parent linking, optional params, positions, and container slot assignment in one call. Returns the handle of the created entity (object handles include path for stable re-resolution) so you can chain set_params / set_keyframe. Note: kind:"shader" targets classical shader chains (Fusion, Colorizer, Xbitmap, …). For node-material edits (Standard node space / Redshift), use apply_graph_description instead. kind:"video_post" attaches a renderer effect (Octane 1029525, Redshift 1036219, Magic Bullet Looks 1054755, …) to a RenderData parent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesEntity kind to create.
nameNoOptional display name.
slotsNoOwner BaseContainer slot ids to link the new shader into (e.g. [3740, 3741] for Octane AOV).
paramsNo{param_id: value} to set after allocation. Lists of 3 numbers become Vectors.
parentNoParent handle. Required for tag (owner object), shader (owner VideoPost / tag / material) and video_post (owner render_data). Optional for object (creates at scene root if omitted).
type_idYesPlugin id. Accepts a numeric id (c4d.Ocube=5159, c4d.Ttexture=5616, Octane renderer=1029525, …) or, for kind='object', an alias string: 'cube', 'sphere', 'cylinder', 'cone', 'torus', 'plane', 'disc', 'pyramid', 'platonic', 'null'.
positionNoRelative position [x,y,z] (objects only).
Behavior4/5

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

With no annotations, description carries full burden. States it returns a handle for chaining, mentions object handles include path for stable re-resolution. Notes position is for objects only. Could be more explicit about side effects or permissions, but covers key behavioral traits adequately.

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?

Concise, front-loaded with main purpose. Every sentence adds essential information. No redundancy or filler. Well-structured for quick comprehension.

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?

Given complexity (7 params, nested objects, no output schema), description covers main points: kinds, parent requirements, return value, special notes on shader. Could elaborate on slots or error handling, but overall sufficiently complete for selection and invocation.

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?

Schema coverage is 100%, baseline 3. Description adds value beyond schema: explains shader kind targets classical chains, type_id accepts aliases for objects, position is relative. These details help the agent use parameters correctly.

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?

Clearly states it is a unified constructor for object, tag, material, shader, video_post. Uses specific verb 'create' and lists key capabilities like parent linking, params, positions, slot assignment. Distinguishes from sibling apply_graph_description by noting it is for classical shader chains, not node-material edits.

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?

Provides explicit guidance on when to use apply_graph_description instead for node-material edits. Notes parent requirements for different kinds (required for tag, shader, video_post; optional for object). Implicitly distinguishes from other creation tools by being the unified constructor.

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/kumoproductions/mcp-cinema4d'

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