Skip to main content
Glama

Manage Clips

clips_manage

List or inspect clips, regenerate, repair visual QA, start export, promote an accepted delivery export, inspect caption words, or apply a verified caption look.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
clipIdNo
formatNomp4
lookIdNo
offsetNo
statusNo
assetIdNoUUID string.
exportIdNoUUID string.
matchTextNo
operationYes
projectIdNoUUID string.
endSecondsNo
layoutModeNo
repairModeNoauto
resolutionNo1080p
workspaceIdNoUUID string.
startSecondsNo
suggestionIdNoUUID string.
selectionModeNo
idempotencyKeyNo
timelineItemIdNo
captionsEnabledNo
confirmVisualQaNo
contentTypeHintNo
captionWordLimitNo
coverFrameSecondsNo
clearWordOverridesNo
maxDurationSecondsNo
minDurationSecondsNo
allowBlockingQaBypassNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / confirmVisualQa
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
    • addedInput schema / properties / exportId
      Added value: +{
      +  "description": "UUID string.",
      +  "format": "uuid",
      +  "type": "string"
      +}
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "list",
      -  "get",
      -  "reselect",
      -  "repair",
      -  "export",
      -  "list_caption_words",
      -  "set_caption_look"
      -]New value: +[
      +  "list",
      +  "get",
      +  "reselect",
      +  "repair",
      +  "export",
      +  "promote_export",
      +  "list_caption_words",
      +  "set_caption_look"
      +]
  2. Changed3 schema fields changed
    • addedInput schema / properties / captionsEnabled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / contentTypeHint
      Added value: +{
      +  "enum": [
      +    "auto",
      +    "podcast",
      +    "tutorial",
      +    "demo",
      +    "generic"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / layoutMode
      Added value: +{
      +  "enum": [
      +    "auto",
      +    "people_first",
      +    "screen_first",
      +    "preserve_full_source",
      +    "prefer_split",
      +    "prefer_focus",
      +    "prefer_tutorial",
      +    "prefer_demo"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

C2.6/5.0
Behavior2/5

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

The annotations indicate this is a mutating, non-idempotent operation, and the description reinforces this with verbs like 'regenerate' and 'promote,' but it does not disclose side effects, prerequisites, or reversibility. For example, 'promote an accepted delivery export' implies a state change but no details are given about what is affected or whether confirmation is needed.

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?

The description is a single sentence that packs many operations into a comma-separated list, making it somewhat run-on but still efficient in length. It is front-loaded with 'List or inspect clips' but the long list of loosely related actions reduces clarity and structure.

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

Completeness2/5

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

For a tool with 30 parameters, 7 enums, and an output schema, the description provides only a high-level operation list. It lacks critical contextual details such as parameter dependencies, operation-specific behaviors, or typical use cases, making it incomplete for an agent to reliably invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 30 parameters and only 17% schema description coverage, the description carries a heavy responsibility to explain parameters, but it names none of them. It does not map operations to required fields (e.g., which params are needed for 'repair' vs 'export') nor explain enums like selectionMode or layoutMode.

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 clearly enumerates the tool's operations with action verbs (list, inspect, regenerate, repair, start export, promote, inspect, apply), making its broad purpose evident. It distinguishes from siblings like clips_get or exports_start by covering a wider range of clip management actions, though the list-like structure prevents a single focused purpose from being stated.

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

Usage Guidelines2/5

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

No guidance is provided on when to use clips_manage versus sibling tools such as clips_get, clips_create, or exports_start. The description only lists operations without explaining which to choose for a given scenario or when a more specific sibling tool would be preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources