Skip to main content
Glama

OpenClip

by app.openclip
OverviewDiscussionsAdmin

List Caption Presets Tool

list_caption_presets
Read-only

List the caption style presets available for rendering. Each preset has a key (pass it as caption_preset to render_clip, or to caption_video where that tool is available), a display name, a short description, and a category. Call this to discover valid caption_preset values before rendering; both tools reject any key not in this list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
caption_presetsYesEvery caption preset render_clip and caption_video accept. Any key not listed here is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / caption_presets / description
      Previous value: -"Every caption preset render_clip accepts. Any key not listed here is rejected."New value: +"Every caption preset render_clip and caption_video accept. Any key not listed here is rejected."
    • changedOutput schema / properties / caption_presets / items / properties / key / description
      Previous value: -"Pass this as `caption_preset` to render_clip."New value: +"Pass this as `caption_preset` to render_clip or caption_video."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "caption_presets": {
+      "description": "Every caption preset render_clip accepts. Any key not listed here is rejected.",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Grouping for the preset, e.g. professional.",
+            "type": "string"
+          },
+          "description": {
+            "description": "What the preset looks like.",
+            "type": "string"
+          },
+          "key": {
+            "description": "Pass this as `caption_preset` to render_clip.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Display name of the preset.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "key",
+          "name",
+          "description",
+          "category"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "caption_presets"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful downstream constraint that render tools reject unknown keys, but beyond that it discloses no pagination, ordering, or completeness behavior for the returned list.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the purpose and followed by the return shape and the routing/validation advice. No filler or restatement of the name/title.

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?

Despite an output schema existing, the description complements it by naming the fields and, more importantly, closing the loop on where the keys are consumed. For a zero-parameter discovery tool, everything an agent needs to select and use it is present.

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?

The tool takes zero parameters, so the baseline is 4 and the schema has nothing to document. The description adds value not present in structured data by explaining what a preset `key` is for and that it maps to the `caption_preset` argument of other tools.

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?

States a specific verb and resource ('List the caption style presets available for rendering') and even enumerates the fields of each returned item (key, name, description, category). An agent can immediately distinguish this discovery tool from other list_* siblings like list_clips or list_agents.

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?

Explicitly says when to call it: 'Call this to discover valid `caption_preset` values before rendering.' It also names the consuming tools (render_clip, caption_video) and gives the reason — both reject keys not in this list — so there is no ambiguity about why or when to invoke it.

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

All OpenClip 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