Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

higgsfield_generate_video

Create a Higgsfield video from a text prompt using connected account login and credits, with an optional API key fallback.

Instructions

Generate a Higgsfield video from a prompt. Prefers the customer's connected Higgsfield MCP account login and subscription credits; api_key is only the Cloud API fallback.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "higgsfield_generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for reproducibility
modelNoOptional Higgsfield model id when using the MCP account path
styleNoSoul Style name (use higgsfield_get_styles to list available styles)
promptYesText description of the video to generate
api_keyNoOptional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available.
durationNoVideo duration in seconds
aspect_ratioNoe.g. 16:9, 9:16, 1:1
negative_promptNoWhat to avoid in the video

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.11
    • changedInput schema / properties / api_key / description
      Previous value: -"Higgsfield API key"New value: +"Optional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available."
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional Higgsfield model id when using the MCP account path",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "prompt"
-]New value: +[
+  "prompt"
+]
  2. Addedv0.1.5

TDQS

B3.4/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 full behavioral burden, and it does disclose the auth-precedence and credit-usage behavior, which is useful. However, it omits significant traits for a video-generation tool: whether generation is asynchronous, that results likely require higgsfield_get_status polling, and any latency/cost expectations.

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?

Two tight sentences, front-loading the core action before the auth nuance. No wasted words, though it could be slightly richer given the tool's complexity.

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?

No output schema and no annotations, so the description is the only source of behavioral context. It covers auth but not the async result-retrieval flow, which is the key missing piece for an agent that needs to actually obtain the generated video.

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 100%, so all 8 parameters are already documented in the schema, and the description's api_key fallback note largely restates the schema's own api_key description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Generate) and resource (Higgsfield video) with the trigger input (prompt). The Higgsfield branding distinguishes it from the many other generate_video siblings (kling, pika, runway), though it does not explicitly name higgsfield_generate_image or explain why one would pick it.

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?

Provides genuine when-to-use guidance for the auth path (prefer connected MCP account, use api_key only as Cloud API fallback), but gives no guidance on choosing this tool over the other video-generation tools in the sibling set.

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