Skip to main content
Glama
quokkapix

quokkapix-mcp

Official
by quokkapix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Process one local video with direct QuokkaPix settings

process_video_with_settings

Process a local video with custom settings for cutting, cropping, converting, compressing, audio extraction, or transcription, and save the resulting media or transcript with a result JSON.

Instructions

Run one local video through window.QuokkaPixVideoAgent.applySettings-compatible settings, save the media or transcript output and write quokkapix-video-result.json.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appUrlNoOptional Video app URL. Defaults to https://video.quokkapix.com/#agent=1.
headlessNo
settingsYesPayload accepted by window.QuokkaPixVideoAgent.applySettings.
inputFileYesAbsolute or client-relative local file path readable by the MCP process. Do not pass remote URLs here.
musicFileNoAbsolute or client-relative local file path readable by the MCP process. Do not pass remote URLs here.
outputDirYesLocal directory where the adapter writes the downloaded output and quokkapix-result.json.
timeoutMsNo
settingsIdNo
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.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the main side effects: processing the video, saving media/transcript output, and writing quokkapix-video-result.json. However, it omits important behaviors like the unlock-token/quote flow, headless execution, potential overwrites, and failure modes, leaving a meaningful transparency gap.

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?

The description is one compact sentence with no filler; every phrase earns its place by naming the input, the settings mechanism, the output artifact, and the result JSON. The primary action is front-loaded, making it easy to parse quickly.

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 9-parameter tool with nested settings, no annotations, and no output schema, a single sentence is insufficient. It does not explain the unlock-token/quote alternative flow, the distinction between settings and settingsId, or runtime controls like headless and timeout. The schema descriptions cover some gaps but not enough to make the tool fully self-explanatory.

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 67%, which sets a baseline of 3. The description reinforces the key ideas of 'local video' and 'settings payload' but adds no new parameter-level meaning for headless, timeoutMs, settingsId, or the quote/unlock flow beyond what the schema already provides.

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?

The description states a concrete action: run one local video through applySettings-compatible settings, save media/transcript output, and write quokkapix-video-result.json. It clearly names the resource, mechanism, and output artifacts, distinguishing it from recipe-based video processing and image-only siblings.

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?

Usage is implied by 'direct QuokkaPix settings' and 'one local video,' but the description never names alternatives such as process_video or process_with_settings, nor does it state when not to use them. An agent has to infer selection criteria from the name and title rather than receiving explicit routing guidance.

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