Pixly

Remove Furniture

remove_furniture

Remove furniture from a photo: empty a room and rebuild the surfaces behind what was taken out, keeping the architecture and camera angle identical — the blank canvas for restaging. By default it also removes the room's own joinery (fitted kitchen, built-in wardrobes, bathroom fixtures); mode 'movable' leaves those alone, and an optional extra takes the floor covering out too, for a full renovation strip-back. Doors always stay. (Declutter is the opposite: it keeps the furniture.) Costs credits from the user's Pixly balance.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	How far to strip the room. 'fitted' (the default) removes the movable contents AND the room's own joinery — the fitted kitchen and its appliances, built-in wardrobes and shelving, and bathroom sanitaryware. 'movable' removes only furniture, rugs, curtains, art, plants and lamps, leaving the kitchen, built-ins, sanitaryware, floor and doors exactly as they are.
`extras`	No	Extra things to take out, for a full strip-back. Only applies with mode 'fitted' and is ignored otherwise: 'floor' takes the floor covering down to bare concrete screed. Omit to keep the floor. Doors always stay, as do walls, ceiling, windows, structural openings and the camera.
`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.
`imageUrl`	No	Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`type`	No
`error`	No
`jobId`	Yes	Pass to get_job to poll
`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
`creditsCharged`	No

Schema Changelog

Changes observed during successful MCP inspections.

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."

Changed2 schema fields changedSep 16, 2026

changedInput schema / properties / extras / description

Previous value: -"Extra things to take out, for a full strip-back. Only applies with mode 'fitted' and is ignored otherwise: 'floor' takes the floor covering down to bare concrete screed, 'doors' removes the door leaves while every frame and opening stays. Omit for neither. Walls, ceiling, windows, structural openings and the camera never change."New value: +"Extra things to take out, for a full strip-back. Only applies with mode 'fitted' and is ignored otherwise: 'floor' takes the floor covering down to bare concrete screed. Omit to keep the floor. Doors always stay, as do walls, ceiling, windows, structural openings and the camera."

changedInput schema / properties / extras / items / enum

Previous value: -[
-  "floor",
-  "doors"
-]New value: +[
+  "floor"
+]

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / extras

Added value: +{
+  "description": "Extra things to take out, for a full strip-back. Only applies with mode 'fitted' and is ignored otherwise: 'floor' takes the floor covering down to bare concrete screed, 'doors' removes the door leaves while every frame and opening stays. Omit for neither. Walls, ceiling, windows, structural openings and the camera never change.",
+  "items": {
+    "enum": [
+      "floor",
+      "doors"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / mode

Added value: +{
+  "description": "How far to strip the room. 'fitted' (the default) removes the movable contents AND the room's own joinery — the fitted kitchen and its appliances, built-in wardrobes and shelving, and bathroom sanitaryware. 'movable' removes only furniture, rugs, curtains, art, plants and lamps, leaving the kitchen, built-ins, sanitaryware, floor and doors exactly as they are.",
+  "enum": [
+    "movable",
+    "fitted"
+  ],
+  "type": "string"
+}

removedInput schema / properties / targets

Removed value: -{
-  "description": "What to take out: omit (or 'auto') to empty the room of everything movable while the room itself — fitted kitchen, built-ins, sanitaryware, floor covering and doors — stays. Otherwise pick any of 'furniture' (free-standing pieces), 'decor' (rugs, curtains, art, plants, lamps), 'kitchen' (the fitted kitchen and its appliances), 'floor' (the floor covering, back to bare screed), 'doors' (door leaves; frames and openings stay) or 'bathroom' (sanitaryware). Walls, ceiling, windows, structural openings and the camera never change.",
-  "items": {
-    "enum": [
-      "auto",
-      "furniture",
-      "decor",
-      "kitchen",
-      "floor",
-      "doors",
-      "bathroom"
-    ],
-    "type": "string"
-  },
-  "type": "array"
-}

Changed1 schema field changedSep 16, 2026

addedInput schema / properties / targets

Added value: +{
+  "description": "What to take out: omit (or 'auto') to empty the room of everything movable while the room itself — fitted kitchen, built-ins, sanitaryware, floor covering and doors — stays. Otherwise pick any of 'furniture' (free-standing pieces), 'decor' (rugs, curtains, art, plants, lamps), 'kitchen' (the fitted kitchen and its appliances), 'floor' (the floor covering, back to bare screed), 'doors' (door leaves; frames and openings stay) or 'bathroom' (sanitaryware). Walls, ceiling, windows, structural openings and the camera never change.",
+  "items": {
+    "enum": [
+      "auto",
+      "furniture",
+      "decor",
+      "kitchen",
+      "floor",
+      "doors",
+      "bathroom"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

AddedAug 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it discloses credit cost, default removal of joinery, the 'movable' mode exception, optional floor strip-back, and invariants like doors staying. There is no contradiction with destructiveHint=false because the tool edits a photo rather than deleting a stored asset.

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?

Three dense sentences front-load the main purpose, then cover variant modes, constraints, and cost. There is no filler; every sentence contributes to correct selection and invocation.

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?

Given the detailed input schema, annotations, and output schema, the description supplies all remaining context: purpose, default behavior, variants, constraints, and cost. An agent has everything needed to invoke it 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 coverage is 100% and the schema already documents mode defaults, extras applicability, and the imageUrl/r2Path alternatives. The description adds emphasis but does not materially extend the parameter semantics.

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?

The description names a precise operation (remove furniture from a photo), explains the resulting output (empty room with rebuilt surfaces, identical architecture/camera), and explicitly contrasts with declutter. This makes it clearly distinguishable from sibling editing tools like declutter_photo.

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?

It frames the tool as the blank-canvas restaging option and gives the key decision rule: Declutter is the opposite and keeps furniture. Mode behavior is also described in enough detail to know when fitted vs movable is appropriate.

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?