Clypmint

Read the timeline

get_timeline

Read-onlyIdempotent

Layers and every overlay. layer_id: one graphic's whole scene, to change it. Cost: Free.

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": "get_timeline"
  }
}

Input Schema

Name	Required	Description
`offset`	No	Where to go on in the layer list, from next_offset.
`captions`	No	true: every caption word as a layer. Left out, caption words are one summary row; get_transcript reads them.
`layer_id`	No	One graphic, read whole.
`video_id`	No	Video; the open one if left out.
`output_id`	No	Output id.
`base_version`	No	Version id.

Output Schema

Name	Required	Description	Default
`code`	No
`cost`	No
`error`	No
`state`	No
`status`	No
`dry_run`	No
`message`	No
`plan_id`	No
`style_id`	No
`video_id`	No
`available`	No
`import_id`	No
`output_id`	No
`studio_url`	No
`version_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026
- removedInput schema / properties / layer_id / pattern
```
Removed value: -"^[A-Za-z0-9:_-]{1,160}$"
```

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / captions / description

Previous value: -"true: every caption word as its own layer. Left out, a run of caption words is one summary row (count, span, first and last id, opening words); get_transcript reads them."New value: +"true: every caption word as a layer. Left out, caption words are one summary row; get_transcript reads them."

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / captions

Added value: +{
+  "description": "true: every caption word as its own layer. Left out, a run of caption words is one summary row (count, span, first and last id, opening words); get_transcript reads them.",
+  "type": "boolean"
+}

Changed1 schema field changedNov 7, 2026

changedInput schema / properties / video_id / description

Previous value: -"The video; the open one when left out."New value: +"Video; the open one if left out."

Changed1 schema field changedNov 6, 2026

addedInput schema / properties / layer_id

Added value: +{
+  "description": "One graphic, read whole.",
+  "pattern": "^[A-Za-z0-9:_-]{1,160}$",
+  "type": "string"
+}

Changed4 schema fields changedNov 6, 2026

changedInput schema / properties / base_version / description

Previous value: -"A version_id to read; the live version when left out."New value: +"Version id."

changedInput schema / properties / output_id / description

Previous value: -"An output (Short, hook, shape); the main video when left out."New value: +"Output id."

changedInput schema / properties / video_id / description

Previous value: -"The video, from list_videos."New value: +"The video; the open one when left out."

changedInput schema / required

Previous value: -[
-  "video_id"
-]New value: +[]

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / output_id / description

Previous value: -"A Short, hook or shape of the video; the main video when left out."New value: +"An output (Short, hook, shape); the main video when left out."

AddedOct 31, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds 'Cost: Free' and clarifies that layer_id returns one graphic's whole scene, but it does not mention pagination/offset behavior or what the default no-argument call returns. With annotations carrying the main behavioral burden, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is short and front-loads the content scope, with no filler. However, the telegraphic sentence fragments ('Layers and every overlay', 'Cost: Free') are harder to parse than a complete sentence and leave meaning implicit. It is concise but not well structured.

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 six-parameter read tool, the description is too terse to be fully complete: it never explains the default behavior, how offset/captions affect results, or the intended timeline-reading workflow. Annotations and the output schema cover safety and return shape, which prevents a lower score, but the description still leaves important usage context to inference.

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 100%, so the baseline is 3. The description adds little beyond the schema: it echoes layer_id as 'one graphic's whole scene' (schema says 'One graphic, read whole') and adds 'to change it,' but does not explain offset, captions, or default video selection beyond what the schema already provides.

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

Purpose3/5

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

The title supplies the verb ('Read') and the description names the resource ('Layers and every overlay'), so the basic read target is inferable. However, the description itself is a fragment and never clearly states that it returns the timeline structure, and 'to change it' muddies whether the tool edits or reads. It does not distinguish this from sibling reads such as get_transcript or get_selection.

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 appears in the description. It does not say when to call this for timeline inspection, when to use layer_id, or when to prefer get_transcript for captions; the only alternative is mentioned inside the schema, not the description.

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

All Clypmint tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?