Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

higgsfield_get_status

Read-onlyIdempotent

Check the status of a Higgsfield generation using its ID, preferring your connected account login with an API key as fallback.

Instructions

Check the status of a Higgsfield generation by ID. Prefers the customer's connected Higgsfield MCP account login; 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": {
      "generation_id": "<generation_id>"
    },
    "name": "higgsfield_get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional Higgsfield Cloud API key for this call. Omit it to use the connected Higgsfield MCP account login when available.
generation_idYesGeneration ID returned by higgsfield_generate_video or higgsfield_generate_image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
    • changedInput schema / required
      Previous value: -[
-  "api_key",
-  "generation_id"
-]New value: +[
+  "generation_id"
+]
  2. Addedv0.1.5

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover readOnly/idempotent/safe. The description adds auth behavior beyond annotations: it prefers the connected MCP account and treats api_key as Cloud API fallback, which is real operational context. It stops short of describing what status values come back.

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 sentences, front-loaded with purpose, no filler.

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 status-polling tool with no output schema, the description does not explain what the returned status looks like or whether polling is expected, leaving a meaningful gap an agent must guess at. Auth is well covered though.

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% and both parameters are documented, including which generate tool produces generation_id. The description largely restates the schema's api_key preference, so 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+resource: 'Check the status of a Higgsfield generation by ID'. This is clearly distinguishable from the generate siblings, though it does not explicitly name them or contrast behavior.

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 'by ID' and the reference to generation IDs from the generate tools, and auth preference (connected login over api_key) is guidance. But there is no explicit when-not or named alternative.

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