CueFrame

List Catalog

list_catalog

Read-onlyIdempotent

Use projection:'component-library' for the unified source-free library page, returned as complete JSON with exact scoped definition/preset/recipe cards and pagination. Choose origin:'builtin' for the maintained builtins or origin:'library' for the authenticated serving home; use libraryKind, category, q, limit and after to filter/page. Preserve each card identity.scope and identity.revision, its source/definition pin or exact recipe document identity; same names/IDs in different scopes remain distinct. Resolve the selected exact source with sourceVersionId (plus builtinCollection for an explicitly selected builtin), never a latest-head or another-home lookup. Presets identify their exact presetVersionId, definition pin and historical document witness; recipes identify their complete exact document and member source pins. This projection contains no source bodies or legacy thumbnail substitution. Omit projection for the historical catalog protocol below. DISCOVER WHAT TO BUILD WITH — list the component catalog: the one built-in primitive (heroText, the behind-subject overlay) plus your org-installed components. Desktop also includes bundled kind:'component-package' entries: these are complete reusable authored packages; insert them with the desktop apply_template tool using placement.template and explicit insert.startTime/idPrefix, media bindings and parameter values. Do not pass their ids to clip.add, get_component_source, or cueframe://component resources. Their draft status does not certify visual review or licensing. For hosted builtin preset/recipe cards, call resolve_builtin_component with the exact collection, id and revision, then apply_template with template: and body:{projectId,documentSha256,insert:{startTime,idPrefix},...}. Hosted tool request fields live under body; desktop tool shapes may differ. The agent-safe default page is 20 entries; use pagination.nextCursor as after, or narrow with category, kind, tier, useCase, mood, q, or intent. Results are recommended-tier-first when filtered. Primitive/installed entries carry the exact placement hint for apply_composition and fixedCopy warnings; use get_component_source to fork a primitive when baked copy must change. Read cueframe://component/{id} for the full primitive/installed prop schema. SCENE SHOTS ARE NOT LISTED HERE: there is no built-in scene primitive, so do not look for one — author a shot with the scene.add op (see cueframe://scene-shot). The wrapper it registers then appears here as an ordinary INSTALLED component under these same rules.

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

Input Schema

Name	Required	Description
`q`	No	Free-text match across id/name/description/intent/useWhen/tags/mood. Recommend-orders results.
`kind`	No	Filter by render kind (component\|transition\|scene).
`mood`	No	Filter to entries whose mood tags include this value (e.g. cinematic, minimal).
`tier`	No	Filter by curation tier (recommended\|standard\|niche).
`after`	No	Opaque cursor from a previous page's nextCursor (forward-only).
`limit`	No	Page size (1..100). Omit to return the whole filtered catalog in one page.
`intent`	No	Alias of `q` framed as recommend-by-intent (e.g. intent=intro). Recommend-orders results.
`origin`	No	With component-library projection, builtin selects immutable builtin cards; library selects the authenticated org's exact serving datastore.
`useCase`	No	Filter to entries whose useCase includes this edit role (e.g. intro, title-over-footage, grade).
`category`	No	Filter to one category bucket (text\|effects\|transitions\|layouts\|backgrounds\|ui-blocks\|scenes).
`projection`	No
`libraryKind`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  }
+}
```
- addedInput schema / properties / limit / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / limit / maximum
```
Removed value: -100
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / limit / type
```
Removed value: -"integer"
```
First observedOct 10, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Beyond annotations that already mark this as a safe read-only listing, the description discloses important behavioral traits: the projection is source-free, draft status does not certify visual review or licensing, results are recommended-tier-first when filtered, and card identity.scope/revision and exact source pinning must be preserved. It also states the agent-safe default page size, pagination cursor behavior, and that scene shots are intentionally absent.

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

Conciseness2/5

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

The description is long, dense, and not front-loaded around the primary action; the high-level purpose appears well after projection-specific instructions. It mixes two catalog protocols, routing guidance, result-field rules, and scene-shot caveats into a single wall of text, with some repetition and capitalization used as structure.

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

Completeness4/5

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

For a complex 12-parameter listing tool with no output schema, the description is largely complete: it explains return-card identity, source-free behavior, draft caveats, pagination, and how to resolve exact preset/recipe sources. The remaining gap is that the historical protocol and full return-card shape are described by implication rather than cleanly separated, so an agent may need to reread to distinguish the two modes.

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 already high at 83%, but the description adds meaningful semantics for key parameters: projection='component-library', origin='builtin' vs 'library', libraryKind filtering, after as pagination.nextCursor, q/intent recommend-ordering, and narrowing by category, kind, tier, useCase, mood, or intent. It also references sourceVersionId and builtinCollection in the result-resolution protocol, though those are not present in the input schema, which slightly muddies the parameter story.

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 eventually states the core action clearly: "list the component catalog: the one built-in primitive ... plus your org-installed components." It also distinguishes the tool from siblings such as apply_template, get_component_source, resolve_builtin_component, and clip.add. However, the purpose is delayed behind a dense projection-specific opening, so it is clear but not front-loaded.

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

Usage Guidelines5/5

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

It explicitly says when to use the component-library projection, when to omit projection for the historical protocol, and how to route builtin preset/recipe cards through resolve_builtin_component then apply_template. It also names alternatives and exclusions, including not passing component-package ids to clip.add, get_component_source, or cueframe://component resources, and directing scene shots to scene.add instead.

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

All CueFrame 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.