Skip to main content
Glama

Add an image/logo or text overlay to the timeline

add_timeline_overlay

Overlay an image or text caption on a video timeline at a specific time and position. Use for adding logos, watermarks, or text overlays to real estate property videos.

Instructions

Overlay an EXISTING image/logo OR a text caption on the timeline at a specific point. For an image, pass imageId (already in the project — url auto-resolved) or a direct url; for text, pass text. position is percent-of-canvas (0-100) from the top-left. Blocked in read-only mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoDirect image url (alternative to imageId).
sizeNoImage scale factor 0-1. Image overlays only.
textNoText caption — provide instead of an image for a text overlay.
s3KeyNo
imageIdNoProject image id to overlay (url auto-resolved).
opacityNo
durationNoSeconds on screen. Default 5.
fontSizeNoText size in px. Text overlays only.
positionNoPercent-of-canvas position from top-left.
fontColorNoText color, e.g. #FFFFFF. Text overlays only.
projectIdYes
startTimeNoSeconds from the start of the movie. Default 0.
Behavior4/5

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

With no annotations, description explains position coordinate system, dual modes, and read-only restriction. But it doesn't mention side effects like conflict resolution or default behaviors.

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?

Three sentences with key information front-loaded. Each sentence adds value without redundancy.

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

Completeness3/5

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

Covers core usage but lacks return value description, error handling, and default values for some parameters (e.g., opacity, size). Given 12 parameters and no output schema, more detail would help.

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?

Adds context beyond schema by grouping parameters into image/text modes and clarifying position interpretation. Schema coverage is 75%, so description complements well.

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 'Overlay an EXISTING image/logo OR a text caption on the timeline at a specific point', distinguishing between image and text overlays. This differentiates it from siblings like add_image_from_file.

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?

Specifies modes for image vs text and mentions blocked in read-only mode. However, it doesn't explicitly guide when to use this vs alternatives like add_timeline_audio.

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/TryReelEstate/reel-estate-mcp'

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