Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

higgsfield_get_styles

Read-onlyIdempotent

Lists and searches Higgsfield models or styles by type and query, using a connected account login with an optional API key fallback.

Instructions

List Higgsfield models/styles. Prefers the customer's connected Higgsfield MCP account login; api_key is only the Cloud API fallback.

Input Schema

NameRequiredDescriptionDefault
typeNoModel type to explore, e.g. image or video (default image)
queryNoOptional model/style search text
actionNoMCP model explorer action (default search)
api_keyNoOptional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.11
    • addedInput schema / properties / action
      Added value: +{
+  "description": "MCP model explorer action (default search)",
+  "type": "string"
+}
    • 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 / query
      Added value: +{
+  "description": "Optional model/style search text",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Model type to explore, e.g. image or video (default image)",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "api_key"
-]New value: +[]
  2. Addedv0.1.5

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds real behavioral context about credential resolution order, which the agent cannot infer elsewhere. It does not mention result caps, pagination, or response shape, keeping it below 5.

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 short sentences with zero filler, and the core purpose is front-loaded before the credential note.

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 read-only list tool with full schema coverage and clear annotations, the definition covers purpose and auth adequately. The only gap is that no output schema exists and the description doesn't hint at what the listing returns, though that is largely self-evident from 'models/styles'.

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 coverage is 100%, so all four parameters (type, query, action, api_key) are already documented, including the api_key fallback semantics. The description mostly restates the api_key rule and adds nothing about 'action' or the meaning of 'type' defaults beyond the schema. Baseline 3 applies.

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 ('List Higgsfield models/styles'), which separates it from the generate/status siblings by verb alone. It does not explicitly name or contrast those siblings, so it stops short of a 5.

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?

The second sentence gives auth-selection guidance (prefer connected MCP login, api_key as fallback), which is useful but is about credentials rather than when to call this tool. No explicit statement that this is the discovery step before higgsfield_generate_image/video, and no exclusions.

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