Skip to main content
Glama
Sign In
Clipwright

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Make a shot candidate

create_candidate

Create one new picture or clip for a specific shot in a faceless-video run to review and keep or discard in a revision. Quote first; delivered candidates are charged even if discarded.

Instructions

Input: the same fields as quote_candidate. A NEW edit_shot run making one picture or clip for one shot of a make_faceless run, to keep or discard in a revision. A delivered candidate is charged its one unit whether it is kept or discarded; one that fails is charged nothing. Repeating an identical request returns the run it started, starting nothing new; pass take 2 for another one. Limits on candidates running and failed are named by the refusal. While shot candidates are closed it answers editing_disabled and charges nothing. Poll get_run. Price: picture: 7 credits per image; clip: 49 credits per clip; clip with a new picture: 56 credits per clip. Quote first with quote_candidate.

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": {
      "run_id": "<run_id>",
      "shot_id": "<shot_id>",
      "operation": "<operation>"
    },
    "name": "create_candidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
takeNo
run_idYes
shot_idYes
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.39.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / operation / description
      Removed value: -"What to generate: one of the operations get_run_shots lists for the shot."
    • removedInput schema / properties / operation / oneOf
      Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "mode": {
-        "const": "retake",
-        "type": "string"
-      }
-    },
-    "required": [
-      "mode"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "description": {
-        "maxLength": 600,
-        "minLength": 1,
-        "type": "string"
-      },
-      "mode": {
-        "const": "new_picture",
-        "type": "string"
-      }
-    },
-    "required": [
-      "mode",
-      "description"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "instruction": {
-        "maxLength": 600,
-        "minLength": 1,
-        "type": "string"
-      },
-      "mode": {
-        "const": "edit_picture",
-        "type": "string"
-      }
-    },
-    "required": [
-      "mode",
-      "instruction"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "mode": {
-        "const": "animate",
-        "type": "string"
-      },
-      "motion": {
-        "maxLength": 300,
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "mode"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties / operation / type
      Added value: +"object"
    • removedInput schema / properties / run_id / description
      Removed value: -"The faceless run whose shot the candidate is for: a succeeded original or revision."
    • removedInput schema / properties / run_id / pattern
      Removed value: -"^run_[a-zA-Z0-9]+$"
    • removedInput schema / properties / shot_id / description
      Removed value: -"The shot to make a candidate for, as get_run_shots names it."
    • removedInput schema / properties / shot_id / pattern
      Removed value: -"^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$"
    • removedInput schema / properties / take / description
      Removed value: -"Take number, 1 by default: the same request and take return the same run; take 2 makes another candidate."
    • removedInput schema / properties / take / exclusiveMinimum
      Removed value: -0
    • removedInput schema / properties / take / maximum
      Removed value: -9007199254740991
  2. Addedv0.29.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses billing semantics (a delivered candidate is charged whether kept or discarded, failures are free), idempotency ('repeating an identical request returns the run it started'), named refusal/limit responses ('editing_disabled', limit refusals), and the polling target (get_run). Nothing here contradicts readOnlyHint=false / destructiveHint=false.

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?

Front-loaded with the resource and scope, then cost, then idempotency, then limits — a sensible priority order with no filler. The telegraphic sentence fragments make it denser than it needs to be but no sentence is wasted.

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?

For a paid mutation with a nested object parameter and no output schema, the description supplies everything an agent needs to call it correctly: cost, quote-first requirement, idempotency behavior, failure charging, and where to poll for results.

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 coverage is 0%, so the description must carry the burden. It explains 'take' as an idempotency-breaking counter and points to quote_candidate for the input field set, which covers run_id/shot_id/operation by reference, but the nested 'operation' object's internal shape is never described.

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 precise verb+resource+scope: 'A NEW edit_shot run making one picture or clip for one shot of a make_faceless run.' It also implicitly separates itself from quote_candidate (pricing only) and from revise_run/make_faceless by naming the underlying operation type.

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

Usage Guidelines4/5

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

Gives an explicit ordering rule ('Quote first with quote_candidate') and a retry rule ('pass take 2 for another one'), plus the disabled-state path. It does not state when a revision (revise_run) is preferable to a new candidate, so it falls just short of full when/when-not coverage.

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

Deploy Server

Other Tools