Skip to main content
Glama
Sign In

ChatCut

by io.chatcut
OverviewDiscussionsAdmin

browse_library

Read-onlyIdempotent

Browse ChatCut Library content, not current-project assets (browse_assets/inspect_asset).

For MG styles use manage_design_style list_presets/get/apply_preset. This tool searches concrete MG instances: references:{kind:"instance",query,facets,styleId?} returns cover collages; ids + parts reads summary/hero/motion/materials/code. The chosen Design Style's nextReferenceSearch supplies related-instance query parameters. Category/query mode below browses ordinary library items.

Built-in entries in this runtime:

  • effects: Rectangle Mask, Circle Mask, Local Mosaic, Magnifying Glass, Gaussian Blur, Gaussian Blur, Dome Magnifier, Tilt-Shift, CRT Retro, ASCII Rain, Camera Shake, Black Overlay (Screen)

  • luts: Sony S-Log3 s709, Canon Log3 to Canon 709

  • transitions: Anticipation Zoom, Clean Line Wipe, Cross Dissolve, Dip to Black, Flash, Impact Shake, Luma Blend, Organic Light Dissolve, Page Curl, Rack Focus, Soft Wipe, Whip Pan, Audio Cross Fade

  • zoom: Slow Push, Slow Pull, Instant, Quick In, Quick Out, Zoom In + Out

Other Library modes:

  • No filters: category counts. category: groups. category + group or query: item lists. limit/offset: pagination.

  • id: selected item details and usage guidance. Lists contain only id/name/category/description.

  • motion-graphics: published and saved templates (group:"favorites"); ids go to manage_template templateId (get, list_assets: properties/defaults, apply).

  • sound-effects: edit_item adds:[{type:"audio",assetId:"library:sound:",fromFrame:}]. Imports/reuses the sound and aligns its anchor to fromFrame.

  • zoom/effects/luts/transitions: edit_item with returned usage guidance.

  • audio-effects: no entries currently.

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

Input Schema

NameRequiredDescriptionDefault
idNoExact Library item id to inspect after search. Returns the chosen item plus usage guidance from this same tool.
groupNoOptional Library group id filter. With category, returns list results from that group.
limitNoMaximum list results to return. Defaults to 10, max 30.
queryNoCase-insensitive search over id, name, category, group, description, and keywords. Supports multi-word queries and common quote/social/card/sound-effect synonyms. Passing query returns a list.
offsetNoList offset for pagination in list mode.
categoryNoOptional Library tab/category filter: motion-graphics, luts, zoom, effects, audio-effects, sound-effects, or transitions.
referencesNoConcrete MG examples only. Search by query/facets; styleId (Design Style UUID) scopes to related instances. Read selected instance ids with parts; continue pendingIds for split details. known contains only returned versions/parts still in context. Browse/read styles with manage_design_style. With an agent workspace, loaded code is also saved as results[].codeFile {path, bytes, properties, width, height, durationInSeconds}, so a new MG can start from a copy of it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description goes further by disclosing return shapes per mode (no filters → category counts, category → groups, list results contain only id/name/category/description) and by enumerating the actual built-in catalog per category, which is runtime state no schema can express. It does not cover failure/empty-case behavior beyond "audio-effects: no entries currently", and much of the mode prose restates parameter semantics.

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?

It is front-loaded correctly — scope and sibling differentiation come first, then mode behavior. But the body is bloated and uneven: a long built-in catalog list (with a duplicated "Gaussian Blur") occupies prime space, and bullet-style fragments interleave with prose, making it longer than the agent needs to select and call the tool.

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?

With 7 parameters, a deep nested references object, and no output schema, the description carries the burden well by explaining each mode's return shape and the downstream handoffs (manage_template, edit_item add payloads, fromFrame anchoring). Minor gaps remain around pagination interplay between top-level limit/offset and the nested references limit/offset, and around what happens when a query matches nothing.

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 schema already documents most parameters, making 3 the baseline. The description adds real meaning for the nested references object (styleId scopes to related instances, parts reads summary/hero/motion/materials/code, known holds only versions/parts still in context) and for id (returns the item plus usage guidance), but these points are also largely mirrored in the schema.

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?

Opening sentence states a specific verb and resource ("Browse ChatCut Library content") and immediately excludes the confusing siblings: "not current-project assets (browse_assets/inspect_asset)". It further splits the tool's own two purposes (MG instance references vs. ordinary library items) and names manage_design_style for the adjacent but different task.

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?

Explicit routing rules throughout: use browse_assets/inspect_asset for project assets, manage_design_style for MG styles, manage_template templateId for motion-graphics templates, edit_item for applying zoom/effects/luts/transitions and sound-effects. The "Other Library modes" block maps each parameter combination to a use case, so an agent knows which call shape to pick rather than inferring it.

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

All ChatCut toolsInspect
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