Skip to main content
Glama
Sign In

Pixly

by app.pixly
OverviewDiscussionsAdmin

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

NameRequiredDescriptionDefault
modeNoHow 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.
extrasNoExtra 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.
r2PathNoStorage path of a photo already in the user's Pixly library (from list_library, or returned by an upload ticket) — the alternative to imageUrl.
imageUrlNoPublic https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required.
listingIdNoA 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.

Output Schema

NameRequiredDescriptionDefault
jobsNoSeveral jobs at once (get_job with jobIds, or a plan's steps): each one's jobId, status and results
noteNo
typeNo
errorNo
jobIdYesPass to get_job to poll
quoteNoPresent when status is "awaiting_confirmation": nothing ran and nothing was charged yet — the price and settings the user is asked to confirm
statusYespending | processing | completed | failed — anything not completed/failed is still running
createdAtNo
resultUrlsNoPresent when completed; valid 7 days
completedAtNo
resultPathsNoStorage path of each result — pass one as r2Path (or beforeR2Path, a photos[] item) to run another tool on this result
creditsChargedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed1 schema field changed
    • 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."
  5. Changed1 schema field changed
    • 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"
+}
  6. Changed1 schema field changed
    • 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."
  7. Changed2 schema fields changed
    • 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"
+]
  8. Changed3 schema fields changed
    • 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"
-}
  9. Changed1 schema field changed
    • 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"
+}
  10. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations are thin on specifics (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), and the description fills the gap well: it discloses the default behavior (joinery also removed), what 'movable' preserves, that the floor extra applies only in 'fitted' mode, that doors always stay, and that the operation costs credits from the Pixly balance. This is meaningful behavioral context an agent cannot infer from the annotations.

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?

The core purpose is front-loaded in the first clause, and each subsequent sentence adds a distinct fact (default behavior, movable mode, floor extra, doors, cost). The prose is dense with em-dashes and parentheticals, but no sentence is filler, so it stays reasonably tight for the amount of behavior being conveyed.

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?

An output schema exists, so return-value explanation is unnecessary. The description covers the mutation's scope, defaults, mode interaction, an extra option, invariants (doors, walls, camera), and the credit cost, which is everything an agent needs to invoke this photo-edit tool 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%, so the schema already documents mode, extras, r2Path, imageUrl, and listingId in detail, including defaults. The description largely restates those semantics in prose (mode default, extras-only-with-fitted, doors stay), adding little beyond what the schema carries, so the baseline of 3 applies.

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 ('remove furniture from a photo') and defines the outcome precisely: emptying the room while rebuilding surfaces behind the removed objects and keeping architecture and camera angle identical. It explicitly distinguishes itself from a named sibling, declutter_photo ('Declutter is the opposite: it keeps the furniture'), so an agent can route correctly 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear use context ('the blank canvas for restaging', 'a full renovation strip-back') and names the opposite sibling (declutter) with the condition that separates them. It does not, however, mention other plausible alternatives such as restyle_room, virtual_staging, or edit_staged_photo, so routing is only partially covered.

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

All Pixly toolsInspect
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