Skip to main content
Glama
kumoproductions

mcp-cinema4d

by kumoproductions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Timeline Marker

create_marker

Creates a named Cinema 4D timeline marker at a frame or time in seconds, with optional color and length, and returns an index for later edits.

Instructions

Create a named timeline marker at a frame (or time in seconds), with optional colour and length, in one call (c4d.documents.AddMarker). Replaces the old workaround of seeking the playhead and firing the 'Create Marker at Current Frame' command, which could only drop unnamed markers. Returns the marker's info including its index handle for set_marker / remove_marker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoMarker label (default empty).
colorNoMarker colour as [r, g, b] floats in 0..1.
frameNoFrame position (mutually exclusive with time_seconds).
time_secondsNoPosition in seconds (alternative to frame).
length_framesNoMarker length in frames (default 0 — a point marker).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.1
    • changedInput schema / properties / color / items
      Previous value: -[
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  },
-  {
-    "maximum": 1,
-    "minimum": 0,
-    "type": "number"
-  }
-]New value: +{
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / color / maxItems
      Added value: +3
    • addedInput schema / properties / color / minItems
      Added value: +3
  2. Addedv0.4.3

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that this is a single-call creation operation, names the underlying API, and describes the return value including the reusable `index` handle. It does not state whether an active document is required, undo behavior, or what constraints apply, which are meaningful gaps for an unannotated mutation tool.

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?

Front-loaded with the verb+resource and efficient overall. The middle sentence contrasting with the old workaround is useful routing context but is the most expendable portion; the final sentence on the return handle is well placed.

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?

With no output schema present, the description correctly explains the return value (marker info plus the `index` handle), which an agent needs to chain into set_marker/remove_marker. Only minor gaps remain, such as the requirement for an active document and undo/reversibility behavior.

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?

Schema coverage is 100%, so the schema already documents each parameter, including the frame/time_seconds mutual exclusivity and colour format. The description restates these at a high level (name, frame or seconds, optional colour and length) without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a named timeline marker') with the key positional variants (frame or time in seconds) and optional attributes, and names the underlying API call. It also distinguishes itself from the old command workaround that only dropped unnamed markers, so an agent can tell it apart from siblings.

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?

Clear context: it explains it replaces the seek-and-command workaround and that unnamed markers were the previous limitation, and it points to set_marker/remove_marker as downstream consumers via the returned index. It stops short of explicit when-not-to-use guidance or prerequisites (e.g., an active document), but the usage framing is strong.

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

Deploy Server

Other Tools