gimp-mcp

Overview Schema Source Related Servers Discussions Admin

Hue / saturation

gimp_hue_saturation

Destructive

Adjust a GIMP layer's hue, saturation, and lightness across all colors or a selected hue range, with one undo step and optional editable filter output.

Instructions

Rotate hue (degrees, -180..180) and change saturation and lightness (-100..100, 0 = unchanged) of a layer, for all colors or one hue range. One undo step.

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": {
      "item": "<item>"
    },
    "name": "gimp_hue_saturation"
  }
}

Input Schema

Name	Required	Description	Default
`hue`	No
`item`	Yes	Item id (layer, group, mask...) e.g. 'item:5@a1b2c3d4'.
`overlap`	No	Blend with neighbouring ranges, 0-100.
`hue_range`	No		all
`lightness`	No
`saturation`	No
`destructive`	No	true: change the layer's pixels (respects the selection). false: add an editable GIMP filter on the layer (pixels untouched, removable, saved in XCF; applied to the whole layer).

Output Schema

Name	Required	Description
`item`	Yes
`filter`	Yes	Id of the editable filter (non-destructive only), verified to exist.
`operation`	Yes	GEGL/GIMP operation that was applied.
`destructive`	Yes	True when the layer's pixels were changed.
`restricted_to_selection`	Yes	True when only the selected area was changed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Adds genuinely useful context beyond the annotations: 'One undo step' tells the agent the edit is reversible in a single history entry, which softens destructiveHint=true. However, it omits the significant behavioral split controlled by the `destructive` flag (pixel edit vs. live editable filter) that the schema only partially carries, and calls the target 'a layer' while the schema allows groups and masks.

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?

A single dense front-loaded sentence with parenthetical ranges plus a short trailing note on undo. No filler, though the trailing 'One undo step' fragment is slightly clipped.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

placeholder

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?

With only 43% schema coverage the description must compensate, and it does partially: it gives units and bounds for hue/saturation/lightness, explains that 0 means unchanged, and clarifies the 'all colors vs one hue range' semantics. It says nothing about `overlap`, `destructive`, or the `item` identifier format.

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 specific verbs and resources (rotate hue, change saturation and lightness) with numeric ranges and scope (a layer, all colors or one hue range). This clearly distinguishes it from sibling effects tools such as gimp_brightness_contrast or gimp_gaussian_blur.

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 description implies when the tool applies ('for all colors or one hue range') but never states when to prefer it over sibling color tools or what prerequisites exist. No explicit when-not guidance or alternative routing is given.

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

Deploy Server