Skip to main content
Glama

timeline_settings

Read and change current timeline settings, including custom resolution, start timecode, and output blanking, while automatically enabling custom settings when values are set.

Instructions

Read/change settings of the current timeline. set applies {key: value} (useCustomSettings is turned on automatically, e.g. {"timelineResolutionWidth":"1080","timelineResolutionHeight":"1920"}). Also sets the start timecode and output blanking ({"Top":px,"Bottom":px,"Left":px,"Right":px}).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timeline_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
searchNo
timeline_nameNo
start_timecodeNo
output_blankingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose a real side effect — `set` automatically turns on useCustomSettings — which is genuinely useful behavioral context. However, it omits permissions/auth requirements, whether changes are reversible, how 'current timeline' is determined, and what the tool returns.

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 read/write capability is front-loaded and the two mutation paths are illustrated with compact inline examples. The nested parenthetical examples make the middle dense, but no sentence is wasted.

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?

For a five-parameter, zero-annotation, no-output-schema mutation tool, the entry is only partly complete. The undocumented `search` and `timeline_name` parameters matter a lot here — an agent cannot tell whether they select the target timeline or filter a result set, which affects whether 'current timeline' is even the operating subject.

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 description coverage is 0% across five parameters, so the description must compensate and only partly does. It adds concrete shape and an example for `set`, plus the {Top,Bottom,Left,Right} key structure for output_blanking, but `search` and `timeline_name` are given no meaning at all, leaving two of five parameters undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence pairs a specific verb with a specific resource ("Read/change settings of the current timeline") and the rest of the description enumerates the concrete settings it touches (resolution via `set`, start timecode, output blanking). It does not name any sibling such as project_settings or render_timeline to differentiate scope, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description explains how to invoke the tool but never says when to prefer it over project_settings or fusion_render_settings, nor when not to use it. The only implicit cue is "current timeline", which hints at scope but leaves the agent to infer the alternative.

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