Skip to main content
Glama
nukIeer

Higgsfield Unlimited MCP

by nukIeer

generate_image

Generate unlimited images using AI models like nano-banana, seedream, and flux. Supports batch generation, aspect ratios, and negative prompts for precise control.

Instructions

Generate a single image, unlimited, across the account pool.

model uses the API path form: v1 models use dashes (nano-banana-2, nano-banana-pro); v2 models use underscores + api_version="v2" (seedream_v5_pro, seedream_v5_lite, flux_2, gpt_image_2, soul_2, kling_omni_image). Unlimited-eligible on a typical plan: nano_banana_2, nano_banana_pro, gpt_image_2, seedream_v5_pro, seedream_v4_5, soul_2, seedream_v5_lite, flux_2, kling_omni_image. Local input_files are auto-uploaded. See list_models and account_info for what's unlimited on your plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
waitNo
modelNo
promptYes
accountNo
timeoutNo
downloadNo
batch_sizeNo
resolutionNo
api_versionNov1
input_filesNo
aspect_ratioNo16:9
extra_paramsNo
input_imagesNo
negative_promptNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses that local input_files are auto-uploaded and discusses model versioning. However, it does not mention whether the tool is destructive, whether it consumes credits, or how it handles errors/timeouts. With no annotations, this is moderate coverage.

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 description is relatively concise with two paragraphs. The first line is front-loaded with the tool's action. The second paragraph, though dense with model names, is necessary for the model parameter. No redundant sentences.

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?

Given the tool has 15 parameters, no parameter descriptions in the schema, and an output schema exists, the description should provide more context on parameter usage. It fails to explain key parameters like negative_prompt, aspect_ratio, extra_params, leaving the agent uninformed.

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

Parameters2/5

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

Schema coverage is 0%, so the description should compensate. It adequately explains the 'model' parameter syntax and unlimited eligibility, but 13 other parameters (seed, account, batch_size, etc.) receive no explanation. The mention of input_files auto-upload is minimal.

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?

The first sentence states 'Generate a single image', clearly indicating the core purpose. However, the description is cluttered with model naming details and doesn't explicitly distinguish this tool from similar ones like generate_image_batch.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus siblings. It mentions unlimited eligibility but does not compare with alternatives like generate_image_batch or generate_storyboard, nor does it specify prerequisites such as account or model availability.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nukIeer/higgsfield-unlimited-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server