Skip to main content
Glama

timeline_validate

Validates timeline JSON and saves it as a new version, returning per-clip durations, spoken text, warnings, and JSON-path errors so edits can be checked before rendering.

Instructions

Validate a timeline JSON and save it as a new version. Returns resolved duration per clip, the spoken text each clip will contain, warnings, and errors with JSON paths. Same name + project continues the same timeline id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timeline": "<timeline>"
    },
    "name": "timeline_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNo
timelineYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3/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 and does disclose good material: it writes a new version, returns per-clip resolved duration and spoken text, and reports warnings/errors with JSON paths. It omits critical behavior for a mutation, notably whether an invalid timeline still persists a version, and whether save=false means validate-only.

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?

Three short sentences, front-loaded with the core action before the return contract. Slight cost: 'Same name + project continues the same timeline id' is terse shorthand that takes a re-read to parse.

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?

There is no output schema, and the description does cover return contents, which is a plus. But for a validation tool whose whole input is an undocumented nested timeline object, the description leaves the caller without enough to construct a valid call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the required `timeline` parameter is a free-form nested object with no documented structure, which the description never compensates for. The `save` boolean's meaning is only weakly inferable from 'save it as a new version' rather than stated.

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?

Specific verb+resource: 'Validate a timeline JSON and save it as a new version' tells the agent exactly what is done, including the persistence side effect. It is distinguishable from read-oriented siblings like timeline_get or analysis_get, though no sibling is named explicitly.

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?

No when-to-use guidance: nothing says whether this should be run before render_start, instead of qa_check, or what prerequisites exist (e.g. an open project). The versioning sentence explains an outcome, not a usage condition.

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