Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

higgsfield_generate_image

Generate a Higgsfield image from a text prompt using the connected account's subscription credits, with an API key as fallback.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
seedNoRandom seed for reproducibility
modelNoOptional Higgsfield model id, e.g. nano_banana_pro
styleNoStyle name (use higgsfield_get_styles to list available styles)
widthNoImage width in pixels
heightNoImage height in pixels
promptYesText description of the image to generate
api_keyNoOptional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available.
resolutionNoOptional Higgsfield resolution, e.g. 1k, 2k, or 4k
aspect_ratioNoe.g. 16:9, 4:3, 1:1, 9:16
negative_promptNoWhat to avoid in the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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 / aspect_ratio
      Added value: +{
+  "description": "e.g. 16:9, 4:3, 1:1, 9:16",
+  "type": "string"
+}
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional Higgsfield model id, e.g. nano_banana_pro",
+  "type": "string"
+}
    • addedInput schema / properties / resolution
      Added value: +{
+  "description": "Optional Higgsfield resolution, e.g. 1k, 2k, or 4k",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "prompt"
-]New value: +[
+  "prompt"
+]
  2. Addedv0.1.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the credential preference order (connected MCP login and subscription credits first, api_key as Cloud API fallback), which is non-obvious behavior. However it says nothing about whether generation is asynchronous and must be polled via the sibling higgsfield_get_status, nor about credit consumption or failure modes.

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 tight sentences with the action front-loaded and the credential behavior second. No filler or restated schema.

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 generation tool with no output schema and an async-looking sibling (higgsfield_get_status), the description should mention that the call returns a job to poll. The credential guidance is good but the lifecycle gap keeps this at an adequate minimum.

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 10 parameters are already documented in the schema; the description adds only the api_key fallback nuance, which the schema also states. Baseline 3 applies 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 and resource ("Generate a Higgsfield image from a prompt") with the provider brand, which distinguishes it from openai_generate_image and stability_text_to_image. It does not explicitly differentiate itself from the sibling higgsfield_generate_video, but the image/video distinction is self-evident.

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 context is implied by the verb and the credential note, but there is no explicit when-to-use guidance against the many other image-generation siblings, nor any when-not condition. Adequate but leaves routing to inference.

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