Pixly

Restyle

restyle_room

Give one or more surfaces of a room a new finish — repaint the walls, change the floor, reface the kitchen cabinets and worktop, retile the bathroom or refinish the furniture — while the room's layout, fittings, windows and camera angle stay exactly as shot. Costs credits from the user's Pixly balance.

Input Schema

Name	Required	Description
`looks`	No	The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, 'own_colour' (walls, cabinets, furniture) with a hex colour in `colours`, or 'material_photo' with a photo of the material in `references`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles (wall tiles only; a bathroom floor is 'floor'): white_metro, zellige_white, marble_large, travertine, green_gloss. floor also takes terrazzo, encaustic_pattern, matt_black_hex. furniture: light_neutral, warm_wood, dark_wood, black_leather.
`notes`	No	Your own description of the finish for a surface, used when that surface's look is "custom" (e.g. "terracotta hex tiles with dark grout"). Set look "custom" and the note together; "custom" with no note falls back to "auto". 120 characters max, and anything in it that is not a description of a finish is ignored.
`r2Path`	No	Storage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl.
`colours`	No	Any colour as a hex code for walls, cabinets or furniture (e.g. {"walls": "#7A8B6F"}), used when that surface's look is "own_colour". The result matches it closely as it would look in the room's light.
`imageUrl`	No	Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required.
`surfaces`	No	Which surfaces get a new finish: 'walls', 'floor', 'cabinets' (fitted joinery plus its worktop and splashback), 'bathroom_tiles' (the tiled walls; a bathroom floor is 'floor') or 'furniture' (upholstery and wood finishes). Omit for walls. The room's layout, fittings and camera never change.
`listingId`	No	A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.
`references`	No	A photo of the material itself — a floor plank, a tile, a fabric swatch, a wallpaper sample — for ONE surface, as the r2Path from create_upload_ticket or list_library (e.g. {"floor": "users/…/oak.jpg"}). Set that surface's look to "material_photo". One photo per run; a close, straight-on photo of the sample works best.

Output Schema

Name	Required	Description
`jobs`	No	Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results
`note`	No
`type`	No
`error`	No
`jobId`	Yes	Pass to get_job to poll
`quote`	No	Present when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm
`status`	Yes	pending \| processing \| completed \| failed — anything not completed/failed is still running
`createdAt`	No
`resultUrls`	No	Present when completed; valid 7 days
`completedAt`	No
`resultPaths`	No	Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result
`creditsCharged`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / listingId

Added value: +{
+  "description": "A property folder (from list_listings or create_listing) to put the result in. Results of a photo that is already in a folder go there by themselves.",
+  "type": "string"
+}

addedOutput schema / properties / jobs

Added value: +{
+  "description": "Several jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results",
+  "items": {
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / quote

Added value: +{
+  "description": "Present when status is \"awaiting_confirmation\": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm",
+  "type": "object"
+}

Changed2 schema fields changedOct 4, 2026

changedInput schema / properties / looks / description

Previous value: -"The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, 'own_colour' (walls, cabinets, furniture) with a hex colour in `colours`, or 'material_photo' with a photo of the material in `references`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles: white_metro, marble_large, terrazzo, matt_black_hex, travertine. furniture: light_neutral, warm_wood, dark_wood, black_leather."New value: +"The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, 'own_colour' (walls, cabinets, furniture) with a hex colour in `colours`, or 'material_photo' with a photo of the material in `references`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles (wall tiles only; a bathroom floor is 'floor'): white_metro, zellige_white, marble_large, travertine, green_gloss. floor also takes terrazzo, encaustic_pattern, matt_black_hex. furniture: light_neutral, warm_wood, dark_wood, black_leather."

changedInput schema / properties / surfaces / description

Previous value: -"Which surfaces get a new finish: 'walls', 'floor', 'cabinets' (fitted joinery plus its worktop and splashback), 'bathroom_tiles' or 'furniture' (upholstery and wood finishes). Omit for walls. The room's layout, fittings and camera never change."New value: +"Which surfaces get a new finish: 'walls', 'floor', 'cabinets' (fitted joinery plus its worktop and splashback), 'bathroom_tiles' (the tiled walls; a bathroom floor is 'floor') or 'furniture' (upholstery and wood finishes). Omit for walls. The room's layout, fittings and camera never change."

Changed4 schema fields changedOct 4, 2026

changedInput schema / properties / colours / description

Previous value: -"Walls only: any paint colour as a hex code (e.g. {\"walls\": \"#7A8B6F\"}), used when the walls look is \"own_colour\". The result matches it closely as that paint would look in the room's light."New value: +"Any colour as a hex code for walls, cabinets or furniture (e.g. {\"walls\": \"#7A8B6F\"}), used when that surface's look is \"own_colour\". The result matches it closely as it would look in the room's light."

changedInput schema / properties / looks / additionalProperties / enum

Previous value: -[
-  "auto",
-  "custom",
-  "own_colour",
-  "warm_white",
-  "crisp_white",
-  "soft_grey",
-  "greige",
-  "warm_beige",
-  "clay_pink",
-  "sage",
-  "soft_blue",
-  "olive_green",
-  "graphite",
-  "deep_navy",
-  "terracotta_walls",
-  "panelling",
-  "wallpaper_textured",
-  "limewash",
-  "microcement",
-  "exposed_brick",
-  "timber_slats",
-  "light_oak",
-  "mid_oak",
-  "wide_ash",
-  "walnut",
-  "herringbone_oak",
-  "grey_plank",
-  "polished_concrete",
-  "stone_tile",
-  "terracotta_floor",
-  "slate_tile",
-  "checker_tile",
-  "carpet_neutral",
-  "white_shaker",
-  "cream_shaker",
-  "handleless_white",
-  "handleless_grey",
-  "charcoal",
-  "matt_black_cabinets",
-  "natural_oak",
-  "walnut_cabinets",
-  "sage_cabinets",
-  "forest_green",
-  "navy_cabinets",
-  "two_tone",
-  "gloss_white",
-  "white_metro",
-  "zellige_white",
-  "white_large",
-  "grey_porcelain",
-  "marble_large",
-  "travertine",
-  "terrazzo",
-  "encaustic_pattern",
-  "matt_black_hex",
-  "slate_dark",
-  "wood_effect_tile",
-  "green_gloss",
-  "light_neutral",
-  "mid_grey_wool",
-  "warm_greige",
-  "cream_boucle",
-  "tan_leather",
-  "black_leather",
-  "green_velvet",
-  "navy_velvet",
-  "rust_velvet",
-  "warm_wood",
-  "dark_wood",
-  "black_metal"
-]New value: +[
+  "auto",
+  "custom",
+  "own_colour",
+  "material_photo",
+  "warm_white",
+  "crisp_white",
+  "soft_grey",
+  "greige",
+  "warm_beige",
+  "clay_pink",
+  "sage",
+  "soft_blue",
+  "olive_green",
+  "graphite",
+  "deep_navy",
+  "terracotta_walls",
+  "panelling",
+  "wallpaper_textured",
+  "limewash",
+  "microcement",
+  "exposed_brick",
+  "timber_slats",
+  "light_oak",
+  "mid_oak",
+  "wide_ash",
+  "walnut",
+  "herringbone_oak",
+  "grey_plank",
+  "polished_concrete",
+  "stone_tile",
+  "terracotta_floor",
+  "slate_tile",
+  "checker_tile",
+  "carpet_neutral",
+  "white_shaker",
+  "cream_shaker",
+  "handleless_white",
+  "handleless_grey",
+  "charcoal",
+  "matt_black_cabinets",
+  "natural_oak",
+  "walnut_cabinets",
+  "sage_cabinets",
+  "forest_green",
+  "navy_cabinets",
+  "two_tone",
+  "gloss_white",
+  "white_metro",
+  "zellige_white",
+  "white_large",
+  "grey_porcelain",
+  "marble_large",
+  "travertine",
+  "terrazzo",
+  "encaustic_pattern",
+  "matt_black_hex",
+  "slate_dark",
+  "wood_effect_tile",
+  "green_gloss",
+  "light_neutral",
+  "mid_grey_wool",
+  "warm_greige",
+  "cream_boucle",
+  "tan_leather",
+  "black_leather",
+  "green_velvet",
+  "navy_velvet",
+  "rust_velvet",
+  "warm_wood",
+  "dark_wood",
+  "black_metal"
+]

changedInput schema / properties / looks / description

Previous value: -"The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, or (walls only) 'own_colour' with a hex paint colour in `colours`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles: white_metro, marble_large, terrazzo, matt_black_hex, travertine. furniture: light_neutral, warm_wood, dark_wood, black_leather."New value: +"The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, 'own_colour' (walls, cabinets, furniture) with a hex colour in `colours`, or 'material_photo' with a photo of the material in `references`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles: white_metro, marble_large, terrazzo, matt_black_hex, travertine. furniture: light_neutral, warm_wood, dark_wood, black_leather."

addedInput schema / properties / references

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "A photo of the material itself — a floor plank, a tile, a fabric swatch, a wallpaper sample — for ONE surface, as the r2Path from create_upload_ticket or list_library (e.g. {\"floor\": \"users/…/oak.jpg\"}). Set that surface's look to \"material_photo\". One photo per run; a close, straight-on photo of the sample works best.",
+  "propertyNames": {
+    "enum": [
+      "walls",
+      "floor",
+      "cabinets",
+      "bathroom_tiles",
+      "furniture"
+    ],
+    "type": "string"
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 4, 2026

addedInput schema / properties / colours

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Walls only: any paint colour as a hex code (e.g. {\"walls\": \"#7A8B6F\"}), used when the walls look is \"own_colour\". The result matches it closely as that paint would look in the room's light.",
+  "propertyNames": {
+    "enum": [
+      "walls",
+      "floor",
+      "cabinets",
+      "bathroom_tiles",
+      "furniture"
+    ],
+    "type": "string"
+  },
+  "type": "object"
+}

changedInput schema / properties / looks / additionalProperties / enum

Previous value: -[
-  "auto",
-  "custom",
-  "warm_white",
-  "crisp_white",
-  "soft_grey",
-  "greige",
-  "warm_beige",
-  "clay_pink",
-  "sage",
-  "soft_blue",
-  "olive_green",
-  "graphite",
-  "deep_navy",
-  "terracotta_walls",
-  "panelling",
-  "wallpaper_textured",
-  "limewash",
-  "microcement",
-  "exposed_brick",
-  "timber_slats",
-  "light_oak",
-  "mid_oak",
-  "wide_ash",
-  "walnut",
-  "herringbone_oak",
-  "grey_plank",
-  "polished_concrete",
-  "stone_tile",
-  "terracotta_floor",
-  "slate_tile",
-  "checker_tile",
-  "carpet_neutral",
-  "white_shaker",
-  "cream_shaker",
-  "handleless_white",
-  "handleless_grey",
-  "charcoal",
-  "matt_black_cabinets",
-  "natural_oak",
-  "walnut_cabinets",
-  "sage_cabinets",
-  "forest_green",
-  "navy_cabinets",
-  "two_tone",
-  "gloss_white",
-  "white_metro",
-  "zellige_white",
-  "white_large",
-  "grey_porcelain",
-  "marble_large",
-  "travertine",
-  "terrazzo",
-  "encaustic_pattern",
-  "matt_black_hex",
-  "slate_dark",
-  "wood_effect_tile",
-  "green_gloss",
-  "light_neutral",
-  "mid_grey_wool",
-  "warm_greige",
-  "cream_boucle",
-  "tan_leather",
-  "black_leather",
-  "green_velvet",
-  "navy_velvet",
-  "rust_velvet",
-  "warm_wood",
-  "dark_wood",
-  "black_metal"
-]New value: +[
+  "auto",
+  "custom",
+  "own_colour",
+  "warm_white",
+  "crisp_white",
+  "soft_grey",
+  "greige",
+  "warm_beige",
+  "clay_pink",
+  "sage",
+  "soft_blue",
+  "olive_green",
+  "graphite",
+  "deep_navy",
+  "terracotta_walls",
+  "panelling",
+  "wallpaper_textured",
+  "limewash",
+  "microcement",
+  "exposed_brick",
+  "timber_slats",
+  "light_oak",
+  "mid_oak",
+  "wide_ash",
+  "walnut",
+  "herringbone_oak",
+  "grey_plank",
+  "polished_concrete",
+  "stone_tile",
+  "terracotta_floor",
+  "slate_tile",
+  "checker_tile",
+  "carpet_neutral",
+  "white_shaker",
+  "cream_shaker",
+  "handleless_white",
+  "handleless_grey",
+  "charcoal",
+  "matt_black_cabinets",
+  "natural_oak",
+  "walnut_cabinets",
+  "sage_cabinets",
+  "forest_green",
+  "navy_cabinets",
+  "two_tone",
+  "gloss_white",
+  "white_metro",
+  "zellige_white",
+  "white_large",
+  "grey_porcelain",
+  "marble_large",
+  "travertine",
+  "terrazzo",
+  "encaustic_pattern",
+  "matt_black_hex",
+  "slate_dark",
+  "wood_effect_tile",
+  "green_gloss",
+  "light_neutral",
+  "mid_grey_wool",
+  "warm_greige",
+  "cream_boucle",
+  "tan_leather",
+  "black_leather",
+  "green_velvet",
+  "navy_velvet",
+  "rust_velvet",
+  "warm_wood",
+  "dark_wood",
+  "black_metal"
+]

changedInput schema / properties / looks / description

Previous value: -"The finish per surface: 'auto', one of the presets below, or 'custom' with your own words in `notes`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles: white_metro, marble_large, terrazzo, matt_black_hex, travertine. furniture: light_neutral, warm_wood, dark_wood, black_leather."New value: +"The finish per surface: 'auto', one of the presets below, 'custom' with your own words in `notes`, or (walls only) 'own_colour' with a hex paint colour in `colours`. A finish that does not belong to its surface falls back to 'auto' (the tool picks one that suits the room; several on auto are made to agree). walls: warm_white, soft_grey, greige, sage, deep_navy. floor: light_oak, walnut, grey_plank, polished_concrete, stone_tile. cabinets: white_shaker, charcoal, natural_oak, forest_green, navy_cabinets. bathroom_tiles: white_metro, marble_large, terrazzo, matt_black_hex, travertine. furniture: light_neutral, warm_wood, dark_wood, black_leather."

Changed1 schema field changedOct 2, 2026

addedOutput schema / properties / resultPaths

Added value: +{
+  "description": "Storage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 23, 2026

changedInput schema / properties / r2Path / description

Previous value: -"R2 object path from an upload ticket (the create_upload_ticket tool, or POST /api/v1/uploads over REST) — the alternative to imageUrl when the photo is a local file."New value: +"Storage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl."

Changed1 schema field changedSep 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "completedAt": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "creditsCharged": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "error": {
+      "type": "string"
+    },
+    "jobId": {
+      "description": "Pass to get_job to poll",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "resultUrls": {
+      "description": "Present when completed; valid 7 days",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "status": {
+      "description": "pending | processing | completed | failed — anything not completed/failed is still running",
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "jobId",
+    "status"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 20, 2026

changedInput schema / properties / r2Path / description

Previous value: -"R2 object path from an upload ticket (POST /api/v1/uploads) — the alternative to imageUrl when the photo is a local file."New value: +"R2 object path from an upload ticket (the create_upload_ticket tool, or POST /api/v1/uploads over REST) — the alternative to imageUrl when the photo is a local file."

AddedSep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations establish the mutation profile (readOnlyHint=false, destructiveHint=false, non-idempotent, open world), and the description adds two genuinely useful facts beyond them: the source photo's layout, fittings, windows and camera angle are preserved unchanged, and the call 'Costs credits from the user's Pixly balance.' That billing disclosure is exactly the kind of non-obvious side effect an agent needs and cannot get from structured fields, though there is no detail on failure or fallback behaviour at the description level.

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?

One front-loaded sentence naming the operation and its surface scope, followed by a short sentence on the preservation constraint and billing. The em-dash list is dense but each item maps to a real capability; no sentence is filler and nothing important is buried at the end.

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 no explanation, and the description covers operation scope, the invariants it preserves, and cost. It does not mention the source-photo requirement or the library/folder plumbing, but those are documented in the schema descriptions of imageUrl, r2Path and listingId, leaving the definition complete enough to call correctly.

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 description coverage is 100% and each of the eight parameters carries a detailed description (including the per-surface preset lists and fallback-to-auto rules), so the baseline is 3. The prose contributes only the notion of 'one or more surfaces,' which merely restates the `surfaces` array and adds no meaning beyond 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 ('give one or more surfaces of a room a new finish') and then enumerates the exact surfaces it can restyle — walls, floor, cabinets, bathroom tiles, furniture — which matches the schema's `surfaces` enum. The phrase 'of a room' plus 'the room's layout, fittings, windows and camera angle stay exactly as shot' separates it cleanly from exterior siblings such as makeover_exterior or replace_lawn.

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 implied rather than stated: an agent can infer this is the tool for changing finishes without moving furniture, and the preservation clause rules out layout edits. But it never names an alternative (virtual_staging, remove_furniture, makeover_exterior) or gives an explicit when/when-not condition, so routing between the many photo-edit siblings is left to inference.

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

All Pixly tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?