Skip to main content
Glama

Add timecode overlay

add_timecode_overlay

Overlay a running HH:MM:SS:FF timecode or countdown onto a video source, with modes for clock, count up, and count down.

Instructions

Overlay a running HH:MM:SS:FF timecode (or a countdown) onto an input TOP as VISUAL pixels — a Text TOP whose text expression re-evaluates every frame, composited 'over' the source with a Composite TOP. Modes: clock (show time since project start — NOT the OS wall clock — as HH:MM:SS:FF), count_up (elapsed time since this overlay was built, from zero), count_down (counts down from target_seconds to 00:00:00:00 and clamps there). The formatter lives in a Text DAT module (mod('fmt').tc(...)) so it re-cooks live inside TD. FPS is probed live (me.time.rate -> project.cookRate -> 60 fallback) and reported. Distinct from sync_timecode, which syncs a CLOCK SIGNAL (no pixels) — this tool draws the timecode into the image. Ends with a Null TOP 'out'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoclock: show total show time (since project start) as HH:MM:SS:FF. count_up: elapsed time since this overlay was built, from 00:00:00:00. count_down: counts down from `target_seconds` to 00:00:00:00 and clamps there.count_up
nameNoBase name for the container COMP that holds the chain.timecode_overlay
colorNoTimecode text color as a hex string, e.g. '#ff3366'.#ffffff
positionNoWhere the timecode text is anchored over the source frame.bottom_left
font_sizeNoTimecode font size in pixels.
source_topYesPath of the input TOP to overlay the timecode onto (e.g. '/project1/moviefilein1'). REQUIRED.
parent_pathNoWhere to build the overlay chain (a COMP path, e.g. '/project1')./project1
target_secondsNocount_down only: seconds to count down from. Ignored in clock/count_up modes.
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description reveals key behaviors: the text expression re-evaluates every frame, composite method, FPS probing, Null TOP output, and mode-specific behaviors (e.g., count_down clamps at zero). No contradictions.

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 detailed but efficiently packed; every sentence serves a purpose (purpose, mode explanation, technical mechanics, sibling distinction). Slightly long but well-structured with key information front-loaded.

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?

The description gives a complete mental model for a tool with 8 parameters, no output schema. It covers purpose, behavior, modes, and technical implementation. The Null TOP output is mentioned. Minor gap: no mention of performance considerations or error scenarios.

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% with descriptions for each parameter. The tool description adds context like the clock mode's timing origin (project start, not OS clock) and the formatter module, but does not provide additional semantics for individual parameters beyond what the schema already offers.

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 explicitly states the tool overlays a timecode as visual pixels onto a TOP, specifying modes (clock, count_up, count_down). It clearly distinguishes from sibling sync_timecode which syncs a clock signal without pixels.

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?

The description directly compares with sync_timecode, indicating when to use this tool (for visual timecode) vs the sibling. However, it does not explicitly state when not to use this tool (e.g., if only clock signal is needed).

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/Pantani/tdmcp'

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