Skip to main content
Glama
seocombat

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Quote a faceless video

quote_faceless
Read-only

Estimate the credit cost of a faceless video before generating it, so you can show the user the price without spending credits.

Instructions

Estimate the credit cost of make_faceless WITHOUT spending credits. Always call this first and show the user the price before make_faceless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoWhat the video is about; the narration is written from it. Required when input_mode is 'brief'; must be absent when it is 'script'.
scriptNoThe narration, read as written. Required when input_mode is 'script'; must be absent when it is 'brief'.
captionsNoBurned-in captions; on by default.
input_modeYes'script' narrates your exact text; 'brief' writes the narration from a short description. Send exactly one of script or brief, matching this mode.
scene_imagesNoOptional images of your own, each placed at a word range or quote of the narration.
style_referenceNoOptional public https image whose visual style the scenes follow.
duration_secondsYesSelected length, 30 to 90 seconds, on a 1/25 s frame boundary. The video ends with its narration, runs at least 25 seconds and may exceed the selection by up to 5 seconds, never beyond 90 seconds. The charge never exceeds the quote. A script must fit this output range.
character_referenceNoOptional public https image of a person or figure to keep consistent across scenes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.21.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds the meaningful behavioral fact that this consumes no credits and is a mandatory pre-step. It does not describe the quote's validity window or what happens if inputs change after quoting, so it stops short of a 5.

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?

Two short sentences, zero filler, with the no-cost guarantee and the call-ordering rule front-loaded.

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 quote tool with no output schema, the description tells the agent everything needed to position it in a workflow. It leaves unspecified the quote's accuracy/persistence relative to the eventual charge, a minor gap given the duration_seconds field already notes the charge never exceeds the quote.

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 input_mode, duration_seconds, script/brief, and image anchors are all already documented in the schema. The description adds no parameter-level detail, so the baseline of 3 is correct.

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 (estimate credit cost of make_faceless) and explicitly differentiates from the sibling it previews by noting it spends no credits. An agent can distinguish it from make_faceless without opening either schema.

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?

'Always call this first and show the user the price before make_faceless' gives an explicit when-to-use rule, an ordering constraint, and the required user-facing step. The alternative (make_faceless) and the condition selecting it are named.

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