Skip to main content
Glama
Sign In
Takes for Mac

Takes for Mac

by marvtub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

higgsfield

Generate or edit videos from inside Takes using 30+ AI video models, assign clips to storyboard shots, and reframe footage; jobs run in the background and save to the session.

Instructions

Make or change a video with Higgsfield (Seedance, Kling, Veo and 30+ more video models) from inside Takes. Video only: images go to make_image. Returns at once; the job runs in the background and the file lands in /generated/-vN, where the Assets tab shows it. With shot= the storyboard shot shows 'Generating' and then plays the clip (aspect ratio = the storyboard format, length = the shot's length, 4-15 s). For a shot, write a real-footage prompt from the shot's do and say (subject, setting, light, camera move); pass image='sketch' to use the sketch only as a composition reference with params {mode: omni_reference}, and say in the prompt that the result is real footage, not a drawing. Change a video: video= with params {mode: video_edit} (Seedance; the takes-alter skill has the method: target frame, 480p draft, check, finalise), or workflow=reframe with aspect_ratio for a new shape. Default model: the one the user picked on Plugins › Higgsfield (higgsfield_status default_model); other models by id (higgsfield model list in Bash; higgsfield model get <id> for params). Each job costs the user's Higgsfield credits: one job per ask, never a batch nobody asked for. Not installed or not signed in: tell the user to open Plugins › Higgsfield.

Input Schema

NameRequiredDescriptionDefault
costNoOnly say what it would cost (free); nothing starts.
nameNoShort file name. Default: shot-<id> or the prompt's first words.
shotNoA storyboard shot id: the clip becomes that shot's video.
imageNoA reference image: a session file, or 'sketch' for the shot's sketch.
modelNoA Higgsfield model id. Leave out for the default.
videoNoA session video to change or reframe (take number or path).
imagesNoMore reference images (session files), after image, in @image order.
paramsNoMore model params, e.g. {"mode": "omni_reference", "resolution": "1080p"}.
promptNoWhat the result shows. Not needed for workflow=reframe.
sessionYesSession as 'Project/folder', an absolute path, or its id (from get_session). An old path still works after a rename or move.
durationNoSeconds (video).
finaliseNoA finished draft job (params draft true) of this session: make its full-size version from the same job. Takes no prompt.
workflowNoreframe (new aspect ratio) or draw_to_video.
end_imageNoLast frame (session file).
start_imageNoFirst frame (session file or 'sketch').
aspect_ratioNoe.g. 16:9, 9:16, 4:5, 1:1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2026.10.29
    • addedInput schema / properties / cost
      Added value: +{
+  "description": "Only say what it would cost (free); nothing starts.",
+  "type": "boolean"
+}
    • addedInput schema / properties / finalise
      Added value: +{
+  "description": "A finished draft job (params draft true) of this session: make its full-size version from the same job. Takes no prompt.",
+  "type": "string"
+}
    • addedInput schema / properties / images
      Added value: +{
+  "description": "More reference images (session files), after image, in @image order.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as a non-read-only, open-world operation, but the description adds substantial behavioral context: it returns immediately while the job runs in the background, the output file lands in a specific path, jobs consume the user's Higgsfield credits, and missing install/login requires user action. This is far beyond what the annotations provide.

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?

The definition is front-loaded with purpose and scoping, and nearly every sentence carries operational value. It is long and dense with semicolon-separated guidance, which is justified by the tool's complexity, but tighter structure could improve scanability.

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

Completeness5/5

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

For a complex 16-parameter video generation/edit tool with no output schema, the description covers return behavior, background execution, output location, shot integration, model defaults, editing workflows, cost implications, and auth/setup failure paths. It gives an agent enough to invoke the tool correctly without needing to infer core behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaningful semantics beyond the schema: using shot=<id> links the clip to a storyboard shot and changes aspect ratio and length, image='sketch' has a specific composition-reference behavior with params {mode: omni_reference}, video with params {mode: video_edit} triggers editing, and workflow=reframe changes aspect ratio. These workflow-level interactions are not obvious from the schema alone.

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 opens with a specific verb and resource: 'Make or change a video with Higgsfield ... from inside Takes.' It explicitly scopes to video only and routes image generation to the sibling make_image, so an agent can distinguish it immediately.

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?

It provides explicit when-to-use guidance for creation, shot-linked video, sketch reference, video editing, reframing, model selection, and cost-only checks. It also states exclusions such as 'Video only: images go to make_image' and guards against unwanted batch jobs.

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