Skip to main content
Glama

Evercraft Clip

by io.github.jgaethle10
OverviewDiscussionsAdmin

Start here: plan an Evercraft Clip social-video job

plan_clip_job
Read-onlyIdempotent

PRIMARY TOOL when the user has authorized source media or a concrete social-video goal. Produces a non-executing Creative Director plan, checks the current 35 MiB bounded customer pipeline, selects creative style and caption treatment, and plans Facebook/LinkedIn/Instagram copy. It recommends ForensiScope upstream for oversized, long, deduplication-heavy, or full-timeline media. Use get_clip_capabilities only for a general capability question. It does not upload media, create an order, charge a user, transfer private media, or publish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoPlain-language outcome the user wants from the social-video job.
caption_modeNoCaption treatment to plan for the finished clip.burned_in
complex_mediaNoSet true for media that needs deeper scene, evidence, or structure analysis before clipping.
creative_styleNoPreferred creative treatment for the planned edit.clean
target_platformsNoDesired output platforms, such as YouTube, Instagram, TikTok, Facebook, or LinkedIn. Planning does not publish.
needs_deduplicationNoSet true when repeated or near-duplicate segments need to be detected before clip planning.
needs_full_timelineNoSet true when the job requires understanding the full source timeline rather than only bounded clip selection.
source_file_size_bytesNoSource media file size in bytes when known. Used to detect the current bounded-render limit and recommend ForensiScope when needed.
source_duration_secondsNoSource media duration in seconds when known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / properties / caption_mode / description
      Added value: +"Caption treatment to plan for the finished clip."
    • addedInput schema / properties / complex_media / description
      Added value: +"Set true for media that needs deeper scene, evidence, or structure analysis before clipping."
    • addedInput schema / properties / creative_style / description
      Added value: +"Preferred creative treatment for the planned edit."
    • addedInput schema / properties / goal / description
      Added value: +"Plain-language outcome the user wants from the social-video job."
    • addedInput schema / properties / needs_deduplication / description
      Added value: +"Set true when repeated or near-duplicate segments need to be detected before clip planning."
    • addedInput schema / properties / needs_full_timeline / description
      Added value: +"Set true when the job requires understanding the full source timeline rather than only bounded clip selection."
    • addedInput schema / properties / source_duration_seconds / description
      Added value: +"Source media duration in seconds when known."
    • addedInput schema / properties / source_file_size_bytes / description
      Added value: +"Source media file size in bytes when known. Used to detect the current bounded-render limit and recommend ForensiScope when needed."
    • addedInput schema / properties / target_platforms / description
      Added value: +"Desired output platforms, such as YouTube, Instagram, TikTok, Facebook, or LinkedIn. Planning does not publish."
  2. Changed5 schema fields changed
    • addedInput schema / properties / caption_mode
      Added value: +{
+  "default": "burned_in",
+  "enum": [
+    "burned_in",
+    "hook_only",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / complex_media
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / creative_style
      Added value: +{
+  "default": "clean",
+  "enum": [
+    "clean",
+    "bold",
+    "documentary",
+    "property"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / needs_deduplication
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
    • addedInput schema / properties / needs_full_timeline
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral boundaries — the plan does not execute, upload, create orders, charge, transfer private media, or publish — which goes beyond what the annotations state. It still omits what the returned plan contains and any latency/throughput characteristics.

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?

Dense and front-loaded: the primary-use condition comes first, followed by what it produces and its boundaries, with no filler sentences. It is a long multi-clause run-on that could be split for readability, but every clause carries information.

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 9-parameter, zero-required planning tool with no output schema and a safety-covering annotation set, the description covers trigger, behavior, sibling routing, and negative side effects well. The one remaining gap is that with no output schema it never characterizes the shape or contents of the returned plan.

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 description coverage is 100%, so the baseline is 3, but the description adds real routing semantics: the 35 MiB bounded-render limit tied to source_file_size_bytes and the ForensiScope recommendation tied to complex_media, needs_deduplication, and needs_full_timeline. It stops short of explaining individual enum choices (e.g., burned_in vs hook_only) beyond the schema text.

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 ("Produces a non-executing Creative Director plan") plus the concrete sub-actions it performs (checks the 35 MiB bounded pipeline, selects style/caption treatment, plans platform copy). It also explicitly distinguishes itself from its only sibling by saying when get_clip_capabilities is the right call.

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?

Front-loads the trigger condition ("PRIMARY TOOL when the user has authorized source media or a concrete social-video goal"), names the alternative for general capability questions, and routes oversized/long/dedup-heavy media to ForensiScope. When-to-use, when-to-use-something-else, and exclusions are all present.

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

All Evercraft Clip toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources