Skip to main content
Glama
Sign In
reelsaw

reelsaw

by osbytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List layer templates

list_layer_templates
Read-only

List reusable layer templates newest first and paginate results to browse layers, bumpers, and timing settings that fit any clip length.

Instructions

Your layer templates (layers that fit any clip length, plus an optional intro / outro), newest first. Returns { items: [{ id, name, layerCount, layers, bumpers, updatedAt }], nextCursor, total, deleted } (nextCursor goes in cursor; deleted = restorable). A layer has the clip-layer fields plus timing { mode, start, end, minSec, maxSec }: head = seconds after the start; tail = seconds before the end (end 0 = the very end); fill = whole clip; relative = fractions 0-1 of the length, held between minSec and maxSec

Input Schema

NameRequiredDescriptionDefault
limitNoTemplates per page (1-500, default 100)
cursorNonextCursor from the previous page; omit for the first page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.26.3
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "nextCursor from the previous page; omit for the first page",
+  "maxLength": 300,
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Templates per page (1-500, default 100)",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Addedv0.23.0

TDQS

A4.4/5.0
Behavior5/5

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

With readOnlyHint already declaring safety, the description adds substantial behavior: newest-first ordering, pagination via nextCursor, a deleted field meaning restorable items, and detailed semantics for layer timing modes. This goes well beyond what annotations provide and gives an agent operational context for interpreting results.

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 front-loaded with the tool's purpose and has no filler, but it is a single dense run-on sentence with many nested clauses. The information density is justified because there is no output schema, though readability could be improved with structural separation.

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

Completeness5/5

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

There is no output schema, so the description must carry return-shape information, and it does: it names the item fields, explains nextCursor/total/deleted, and defines the timing object used by layers. For a read-only listing tool with only two simple parameters, this is complete enough for an agent to call and interpret it correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics beyond the schema by explaining that nextCursor goes into cursor when paging, which clarifies how the pagination parameter is meant to be used.

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 opens with a specific verb-and-resource pair: it lists the caller's layer templates, defines them as reusable layers plus optional intro/outro, and states the default ordering (newest first). That clearly separates it from sibling mutation tools like save_layer_template, update_layer_template, apply_layer_template, and delete_layer_template.

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

Usage Guidelines3/5

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

Usage is implied by the verb 'Your layer templates' and by the pagination details, but there is no explicit when-to-use guidance, prerequisite note, or alternative mentioned. An agent can infer this is the listing/read tool, but the description does not route it against alternatives such as get_clip or apply_layer_template.

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

Deploy Server

Other Tools