Skip to main content
Glama

List C4D Entities

list_entities

Enumerate Cinema 4D scene entities by kind (objects, materials, tags, etc.) with filters and compact summaries, enabling targeted inspection before modifying parameters.

Instructions

Enumerate scene entities of a given kind. Returns compact summaries (name, type_id, type_name, plus kind-specific fields — is_active for take / material / render_data). For kind=object also supports type_ids / tag_types / max_depth filters and include_tags / include_params to read data inline — so you can find 'all cubes with a Ttexture tag and their position in one call' without falling back to exec_python. Use this first to find what exists before describe/set_params. Note: kind=shader walks classical shader chains; for node-material graphs use list_graph_nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindYesEntity kind to list.
ownerNoOwner handle (required for kind=shader).
objectNoFilter tags to this object name (only for kind=tag). Omit to list tags on all objects.
type_idsNo(kind=object) Keep only objects whose GetType() is in this set (e.g. [5159] for cubes).
max_depthNo(kind=object) Skip objects deeper than this (root=0). Default: unlimited.
tag_typesNo(kind=object) Keep only objects carrying a tag whose type id is in this set (e.g. [5616] for Ttexture).
object_pathNoFilter tags to this object path (only for kind=tag). Use when the name is not unique.
render_dataNoRender data name (required for kind=video_post).
include_tagsNo(kind=object) Attach `tags: [{type_id, type_name, name}, ...]` to each match.
name_patternNoOptional regex to filter results by name (e.g. "^VFX_Shot00[2-9]$").
include_paramsNo(kind=object) Parameter ids to read per match. Returned under `params: {param_id: value}`.
Behavior4/5

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

Describes output format, kind-specific fields, and inline data options. No annotations provided; description adequately covers behavior but could mention potential output limits.

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?

Single, front-loaded paragraph with no wasted words; each sentence adds essential information.

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

Completeness5/5

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

Fully explains output, filters, and special cases for shaders/node-materials. No output schema needed as description covers return structure.

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%, but description adds meaningful context like examples ('all cubes with Ttexture tag') and clarifies parameter usage for different kinds.

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 it enumerates scene entities of a given kind, lists return fields, and distinguishes from sibling tools like describe, set_params, and list_graph_nodes.

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

Usage Guidelines5/5

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

Explicitly advises to use first before describe/set_params, and for shader kind directs to list_graph_nodes, providing clear context and alternatives.

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