Skip to main content
Glama

catalog_list

Read-only

Lists available timeline assets by kind—components, styles, transitions, looks, sfx, music, luts, caption presets, brand kits, and fonts—so you can choose what to add to a video edit.

Instructions

List what timelines can use: components (text overlays + animated graphics + custom fx, with prop schemas), styles (saved edit styles), transitions, looks, sfx, music, luts, captionPresets, brandKits, fonts.

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": {
      "kind": "<kind>"
    },
    "name": "catalog_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that the description adds no behavioral context — nothing on result volume, whether prop schemas make responses large, or whether listings are project-scoped. For a read-only discovery call the bar is low, but almost nothing extra is offered.

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?

One sentence, front-loaded with the verb and purpose, then a compact enumeration that maps one-to-one onto the enum. The dense parenthetical list is slightly heavy but every token corresponds to a real enum value, so nothing 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?

With no output schema, the description is the only place return shape could be described, and it only hints at it ("with prop schemas" for components). An agent still does not know the structure of returned entries or how large a listing may be, which matters for a discovery tool.

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 0%, so the description must carry the parameter. It does: the enumerated kinds mirror the `kind` enum and parenthetical glosses explain the ambiguous ones ("components (text overlays + animated graphics + custom fx, with prop schemas)", "styles (saved edit styles)"), which meaningfully disambiguates the choice.

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 description opens with a specific verb ("List") and defines the resource as the set of assets timelines can consume, then enumerates every kind. It is immediately distinguishable from write-side siblings like style_save or fx_create, though it never names them explicitly.

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 only implied: an agent can infer this is a discovery tool to call before referencing components, styles, or audio. There is no explicit when-to-use, no prerequisites, and no statement of whether the catalog is global or scoped to the open project.

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