Skip to main content
Glama

remove_background

Removes the background from a previously generated picture, updates the saved image, and optionally places the cut-out in a shot or the Media bin; credit use requires confirmation.

Instructions

Take the background off a picture made before (generated_pictures id) with Higgsfield's remover; the saved picture is changed. Uses a little of the person's Higgsfield credits: the first call only says so; call again with confirm: true after they agree. Optionally puts the result into a shot or the Media bin (as). For free trimming, cropping or flipping of a picture already in a shot, use cutout.

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": {
      "id": "<id>"
    },
    "name": "remove_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
asNoWhere to put the cut-out; leave out to only change the saved picture.
idYesA picture id from generated_pictures.
shotNoShot id (from get_project). Default: the shot on screen.
confirmNotrue only after the person agreed to spend the credits.
replaceNoA cast member id in that shot whose picture this replaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.2
    • addedInput schema / properties / confirm / description
      Added value: +"true only after the person agreed to spend the credits."
    • addedInput schema / properties / id / description
      Added value: +"A picture id from generated_pictures."
  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?

Annotations only mark this as a non-read-only, non-idempotent, open-world write. The description adds materially: the saved picture is mutated in place, the call consumes Higgsfield credits, and a confirmation gate is required before the charge. That is exactly the cost/mutation context annotations cannot convey.

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-loaded with the action and the cost warning, and every clause carries information (source, mutation, credits, confirm gate, placement, alternative). It is a single dense run-on sentence chain, so scannability is slightly reduced, but there is no filler.

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 5-parameter mutating tool with no output schema, the description covers cost, confirmation, in-place mutation, optional placement, and the alternative tool. It does not clarify the interaction between 'replace' and 'shot' (e.g. whether replace implies the on-screen shot) or what happens if credits are insufficient, leaving a small gap.

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. The description goes beyond it by explaining the semantics of 'confirm' (second call after the person agrees) and 'as' (optionally placing the cut-out into a shot or the Media bin), which are the two parameters most likely to be misused.

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 ('take the background off a picture'), identifies the input source ('generated_pictures id') and the engine ('Higgsfield's remover'), and explicitly contrasts itself with the sibling 'cutout'. An agent can distinguish this from cutout 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 when-to-use routing: use cutout for free trimming/cropping/flipping of a picture already in a shot, use this for background removal. It also spells out the required two-step flow (first call to quote, then confirm:true after agreement) rather than leaving it to inference.

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