Skip to main content
Glama

relight

Apply a text-described lighting change to a photo-real picture by file path or generated ID, producing a new image while keeping the original; confirm credits before processing.

Instructions

Higgsfield relights a picture photo-real: everything stays, only the light changes (like the Thumbnail studio's Make it real). Give a picture file path or a generated picture id, and the light in words. A new picture is made; the original stays. Spends the person's Higgsfield credits: the first call (without confirm) only returns the price and credits left; ask the person, then call again with the same arguments and confirm: true. Waits up to about 50 s; if it isn't done, call picture_status. The result goes to media, a shot's background, or nowhere. To light a shot in the app itself (free), use light.

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": {
      "light": "<light>"
    },
    "name": "relight"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA generated_pictures id instead of a path.
putNoDefault media.
pathNoFull path of a PNG, JPG or WebP on this computer. Or give id.
shotNoShot id (from get_project). Default: the shot on screen.
tallNoMake it 9:16 instead of 16:9.
lightYesThe light, like 'warm low sun from the left, soft blue fill'.
confirmNotrue only after the person agreed to the price.
qualityNoDefault 2k. About 1.5 / 2 / 3 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / confirm / description
      Added value: +"true only after the person agreed to the price."
    • addedInput schema / properties / path / description
      Added value: +"Full path of a PNG, JPG or WebP on this computer. Or give id."
    • addedInput schema / properties / quality / description
      Added value: +"Default 2k. About 1.5 / 2 / 3 credits."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: it discloses that credits are spent, that the first call without confirm only quotes a price and remaining credits, that the call blocks for roughly 50 s, that the source image is preserved, and where the result lands (media, a shot background, or nowhere). Those are exactly the cost, latency, and side-effect facts an agent needs before committing.

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?

Front-loads the core action and its invariant (only the light changes, original preserved) before the cost and flow details, and every sentence carries operational weight. It is slightly dense and the parenthetical 'like the Thumbnail studio's Make it real' is an unexplained cross-reference that adds little for an agent.

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 an 8-parameter mutation with no output schema, it covers cost, latency, source preservation, output destination, and the escalation path to picture_status. What it leaves thin is the return value itself and how the quoted price maps to the quality tiers, which the agent must infer from the schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning on top: 'path or id' as mutually substitutable inputs, 'light' as a natural-language prompt, 'put' as the destination selector, and 'confirm' as a price gate that must be preceded by asking the person. The one gap is that 'tall', 'shot' defaults, and quality/credit tradeoffs are only documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Higgsfield relights a picture photo-real') plus the precise semantic contract: everything stays, only the light changes, a new picture is made and the original stays. It also names the sibling 'light' and marks it as the free in-app alternative, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit input options (a file path or a generated picture id, plus the light described in words) and an explicit exclusion: use 'light' instead to light a shot in the app for free. It also prescribes the two-call confirm flow and routes long runs to picture_status, so the when and the how are both covered.

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