Skip to main content
Glama
Sign In
gimp-mcp

gimp-mcp

by mhbxyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Move layer (offsets)

gimp_set_layer_offsets

Sets a layer or group's top-left corner to exact x/y pixel coordinates, allowing negative or off-canvas placement, in one undo step.

Instructions

Place a layer or group so its top-left corner is at (x, y) in image pixels (may be negative or outside the canvas). Lossless. Refused with LOCKED when its position is locked. 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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "gimp_set_layer_offsets"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
itemYesItem id (layer, group, mask...) e.g. 'item:5@a1b2c3d4'.

Output Schema

NameRequiredDescriptionDefault
xYesOffset of the layer's top-left corner in image pixels.
yYes
idYes
kindYes
maskYes
modeYesGIMP layer mode nick, e.g. 'normal', 'multiply'.
nameYesLayer name. GIMP keeps names unique within an image ('Title #1').
locksYes
widthYes
heightYes
parentYesId of the parent group, null at the top level.
opacityYes0-100.
visibleYes
childrenNoChild layers of a group, top-most first; null for non-groups.
has_alphaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • changedOutput schema / $defs / LayerNode / properties / kind / enum
      Previous value: -[
-  "layer",
-  "group",
-  "text"
-]New value: +[
+  "layer",
+  "group",
+  "text",
+  "vector",
+  "link"
+]
    • changedOutput schema / properties / kind / enum
      Previous value: -[
-  "layer",
-  "group",
-  "text"
-]New value: +[
+  "layer",
+  "group",
+  "text",
+  "vector",
+  "link"
+]
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only cover readOnly/openWorld/destructive, not much else. The description adds real behavioral context: coordinates may be negative or outside the canvas, the operation is lossless, it is refused with LOCKED when the position is locked, and it costs one undo step. That is meaningful beyond what is annotated, though nothing is said about what happens with layer groups' children or masks.

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?

Four short clauses, front-loaded with the operation and coordinate meaning, then the failure mode and undo cost. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be described, and the description covers the key gotchas (negative coordinates, LOCKED refusal, undo). The only meaningful omission for a 3-parameter mutation tool is the layer-vs-mask scope of item and any image/context requirement.

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 low (33%), and the description fully compensates for x and y by explaining that they are image-pixel coordinates for the top-left corner, possibly negative/off-canvas. However, it says 'layer or group' while the schema also lists masks, leaving item semantics partially unresolved for masks and for what identifier form is expected.

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 concrete verb (place/set offsets) and resource (layer or group), plus the exact coordinate semantics via 'top-left corner is at (x, y) in image pixels.' It is clear in isolation, but it never distinguishes itself from the sibling gimp_move_layer, which an agent could plausibly confuse with this tool.

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 is only implied by the operation itself; there is no statement of when to use this versus gimp_move_layer or gimp_set_layer_properties, and no prerequisites (e.g., the layer must belong to an open image).

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