Skip to main content
Glama
quokkapix

quokkapix-mcp

Official
by quokkapix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Process one local video with QuokkaPix

process_video

Process local videos for cutting, cropping, converting, compressing, extracting audio, or transcribing, and get a duration quote before unlocking with a token to keep media local.

Instructions

Open Video in local Chromium and keep media local. Without unlockToken, return an exact duration/transcription quote before paid work; retry the same call with the product-specific token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appUrlNoOptional Video app URL. Defaults to https://video.quokkapix.com/#agent=1.
recipeNoQuokkaPix Video recipe with settings and optional expected-result QA.
headlessNo
recipeIdNoOfficial id from list_video_recipes. Provide recipeId or recipe.
inputFileYesOne local video path uploaded through the browser file input.
musicFileNoOptional local audio/media path for mix or replace-audio recipes.
outputDirYesLocal directory where the adapter writes the downloaded output and quokkapix-result.json.
timeoutMsNo
unlockTokenNoProduct-specific x402 unlock token. Omit it to receive a local duration-based quote before processing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.1
    • addedInput schema / properties / unlockToken
      Added value: +{
+  "description": "Product-specific x402 unlock token. Omit it to receive a local duration-based quote before processing.",
+  "minLength": 16,
+  "type": "string"
+}
  2. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / timeoutMs / maximum
      Previous value: -1800000New value: +3600000
  3. Addedv0.5.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does meaningfully disclose behavior: it uses local Chromium, keeps media local, avoids paid work until an unlockToken is provided, and returns a duration/transcription quote first. It does not describe the post-token success behavior, but outputDir's schema description already indicates where results are written.

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 sentences with no filler. The first sentence front-loads the core local-processing behavior, and the second sentence gives the token/quote protocol. Every clause adds information.

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

Completeness3/5

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

For a 9-parameter tool with a nested recipe object and no output schema, the description leaves the post-token output path implicit and does not explain recipe selection or how this differs from process_video_with_settings. The schema compensates for parameter details, and the two-step quote/token flow is enough to make a correct first call, but notable gaps remain.

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 schema already documents most parameters, and the description adds genuinely useful unlockToken semantics: omitting it triggers a quote, including it authorizes paid processing. That is beyond the schema's plain type/minLength information. It does not enrich headless or timeoutMs, but those are minor given the schema's type/range constraints.

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 names the concrete action: open a local video in local Chromium and keep media local. It is clearly about video processing with QuokkaPix, but it only weakly differentiates from the sibling process_video_with_settings and does not explicitly state the recipe-driven processing role.

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

Usage Guidelines3/5

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

It provides actionable payment-flow guidance: omit unlockToken to receive a quote, then retry the same call with the product-specific token. However, it gives no when-to-use versus process_video_with_settings or process_images, and no exclusions or alternative routing.

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