Skip to main content
Glama
Sign In
seocombat

Clipwright

by seocombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Quote a reference analysis

quote_analysis
Read-only

Estimate the credit cost and check for an existing analysis before starting a full or data analysis of an MP4, Instagram, or TikTok source; returns 0 when a replay is available.

Instructions

Price analyze_reference for an asset_id or a source_url and a mode before starting it: credits_estimate is what a start holds and charges once it succeeds (70 full, 10 data), 0 when the asset or the reel already has an analysis in that mode that a start would answer (replays_analysis_id). A YouTube or unknown link is refused here too. Free; starts nothing.

Input Schema

NameRequiredDescriptionDefault
modeNofull (default, 70 credits): the reference_profile. data (10 credits): duration, size, timed transcript, hook and a 3×3 frame sheet, without the vision pass
asset_idNoasset_id of an MP4 asset of this account, at most 120 s and 100 MiB
source_urlNoinstead of asset_id: an Instagram reel or post link (instagram.com/reel/<code>, /reels/<code>, /p/<code>) or a TikTok video link (tiktok.com/@<user>/video/<id>, vm.tiktok.com/<code>); YouTube is refused

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.36.0
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "full (default, 70 credits): the reference_profile. data (10 credits): duration, size, timed transcript, hook and a 3×3 frame sheet, without the vision pass",
+  "enum": [
+    "full",
+    "data"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / source_url
      Added value: +{
+  "description": "instead of asset_id: an Instagram reel or post link (instagram.com/reel/<code>, /reels/<code>, /p/<code>) or a TikTok video link (tiktok.com/@<user>/video/<id>, vm.tiktok.com/<code>); YouTube is refused",
+  "format": "starts_with",
+  "maxLength": 2048,
+  "pattern": "^https:\\/\\/.*",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "asset_id"
-]
  2. Addedv0.35.0

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/non-destructive, and the description adds the credit model: 70 full / 10 data, what a start holds and charges, 0 when a replay would satisfy the start (replays_analysis_id). That's genuine behavioral context beyond structured fields.

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?

Front-loaded with the key verb, but it's a single dense run-on sentence with nested parentheticals that slows parsing. Every clause carries information, but structure could be cleaner.

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 no output schema, the description helpfully names the return fields (credits_estimate, replays_analysis_id) and their semantics. For a 3-param read-only pricing tool this is nearly complete; minor gap in not stating the exact shape of the quote response.

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?

Schema coverage is 100% so baseline is 3, but the description links mode to concrete credit costs and the replay-eligibility condition, giving meaning the enum alone doesn't convey. It doesn't re-explain the asset_id format, which is fine given schema richness.

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?

States a specific verb+resource: price/quote analyze_reference for asset_id or source_url, prep before starting. Implicitly distinguishes itself from analyze_reference (which starts) and get_reference_analysis (which retrieves), though it never names siblings explicitly. An agent can infer it's the dry-run pricing step.

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?

'before starting it' establishes when to call, and 'Free; starts nothing' reinforces it's a pre-flight check. It also states YouTube or unknown links are refused, which sets invocation boundaries. No explicit exclusion naming the alternative quote/get tools, so not a 5.

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