Pixly
Server Details
Every visual AI tool for property listings — staging, enhancement, decluttering, cinematic video.
- Status
- Healthy
- Uptime
- 99.8% over 57 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 31 tools
Each tool has a distinct primary action, but the large editing family contains adjacent tools (virtual_staging vs edit_staged_photo vs restyle_room; touch_up_exterior vs replace_sky/replace_lawn) whose boundaries must be read carefully from descriptions. The video tools are similarly close (cinematic_motion, photo_to_video, flythrough_video, before_after_reel) but are largely separable by input requirements.
Most names follow a snake_case verb_noun pattern (remove_furniture, replace_sky, draw_floor_plan, get_job), with minor deviations like upscale_hd and touch_up_exterior. Several names are noun phrases rather than verb_noun (cinematic_motion, virtual_staging, day_to_night, photo_to_video, before_after_image), which slightly breaks the pattern but remains predictable.
31 tools is well beyond the recommended 3-15 range and places a heavy selection burden on the agent, even though the domain is broad. While many tools are distinct and earn their place, the surface is large enough that accidental misuse is likely.
Coverage is broad and professional: staging, decluttering, furniture removal, sky/lawn/season edits, floor plans, video, credits, uploads, library listing, watermarking and blurring. Minor gaps exist (no library deletion, no job cancellation, no explicit batch workflow), but agents can work around them.
Available Tools
35 toolsbefore_after_imageBefore & After ImageInspect
Free (no credits): one comparison image from a before and an after photo of the same place — e.g. an empty room and its virtual staging, a daylight shot and its dusk version, a room before and after a restyle. Side by side, stacked, or split by a line; original shape, square, 4:5 or 9:16. Write the labels in the user's language. Returns a finished image at once.
| Name | Required | Description | Default |
|---|---|---|---|
| aspect | No | Shape of the image: original (follows the photos), 1:1 square, 4:5 Instagram post, 9:16 Stories/Reels. | original |
| labels | No | Show the Before / After labels. | |
| layout | No | side = next to each other, stack = one above the other, vsplit = one frame split by a vertical line, diagonal = split by a slanted line. | side |
| 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. | |
| afterLabel | No | Label text for the after photo, in the user's language (default "After"). | |
| afterR2Path | No | Storage path of the after photo — the alternative to afterImageUrl. | |
| beforeLabel | No | Label text for the before photo, in the user's language (default "Before"). | |
| beforeR2Path | No | Storage path of the before photo — the alternative to beforeImageUrl. For a Pixly result, its original photo is the job's source. | |
| afterImageUrl | No | The AFTER photo (e.g. the staged room, the dusk version). Public https URL or data: URI; or afterR2Path. | |
| beforeImageUrl | No | The BEFORE photo (e.g. the empty room, the daylight shot). Public https URL or data: URI; or beforeR2Path. |
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 |
before_after_reelBefore & After VideoInspect
Before and after video: animate a before→after transformation (e.g. empty room → staged, or a renovation, or a daylight photo → its Day to Night version with videoIntent day_to_night) into a social-ready reveal reel from two photos. Both photos are required. Only have one? Make the other first with a photo tool — virtual_staging (empty room → furnished), remove_furniture (furnished → empty), day_to_night, restyle_room, makeover_exterior and the other edit tools — and pass its result as afterImageUrl (or beforeImageUrl). Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Video shape. original (default) keeps the photos' own shape; 9:16, 16:9 or 1:1 crop both photos, centred, to that shape first. | original |
| 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. | |
| afterR2Path | No | R2 path of the end frame — the alternative to afterImageUrl. | |
| revealStyle | No | How the transformation is revealed | smooth |
| videoIntent | No | staging_reveal: an empty room becoming a furnished one (or a renovation). day_to_night: Before is a daylight photo and After its dusk version (a Pixly Day to Night result and its original) — the video turns day into the lit evening; revealStyle does not apply. | staging_reveal |
| beforeR2Path | No | R2 path of the start frame — the alternative to beforeImageUrl. | |
| afterImageUrl | No | End frame (e.g. the staged result) — https URL or data: URI | |
| beforeImageUrl | No | Start frame (e.g. the empty room photo) — https URL or data: URI | |
| durationSeconds | No |
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 |
blur_faces_platesBlur Faces & PlatesInspect
Free (no credits): find and blur people's faces and car licence plates in property photos before they're posted — street and exterior shots, open houses. Automatic detection, 1–5 photos per call. Says so when nothing is found.
| Name | Required | Description | Default |
|---|---|---|---|
| faces | No | ||
| style | No | blur | |
| photos | Yes | The photos, 1–5. Each item takes imageUrl or r2Path. | |
| plates | No | ||
| 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. |
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 |
cinematic_motionCinematic MotionInspect
Photo to video: turn a single listing photo into a short cinematic real estate video with a professional camera move (zoom, orbit, fly-through, crane up…). No second frame needed. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| format | No | Video shape. original (default) keeps the photo's own shape; 9:16 or 16:9 crop the photo, centred, to that shape before it is animated. | original |
| 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. | |
| direction | No | The direction the camera travels, for the moves that have one (orbit, pan, drone-orbit). 'left-to-right' sends the camera rightward, 'right-to-left' leftward. Ignored by every other move; omit to use the move's own default. | |
| 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. | |
| cameraMove | No | Camera-move preset | zoom |
| durationSeconds | No | Clip length in seconds. Leave out for the default 5 s; 10 s costs about twice as much — use it only when the user asks for a longer video. |
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 |
create_listingNew Property FolderInspect
Create a property folder before work on a whole property (a set of listing photos, a walkthrough). Ask the user once which property it is and pass that as title; if they skip, leave title out. Pass the returned listingId to the tools so their results land in it. Costs nothing.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | The property in the user's words, e.g. "12 Oak St" — leave out if they skipped the question |
create_upload_ticketUpload a Local PhotoAInspect
Get a presigned upload URL for a LOCAL image file — the one case a URL can't cover. PUT the file to uploadUrl with the same Content-Type, then pass the returned r2Path to a generation tool instead of imageUrl. Ticket expires in 1 hour.
| Name | Required | Description | Default |
|---|---|---|---|
| filename | Yes | Original filename, used for the extension | |
| sizeBytes | No | Exact byte size of the file. Recommended: when given it is signed into the URL, so the upload is bounded server-side. | |
| contentType | Yes | MIME type the PUT request will send |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (readOnlyHint=false, openWorldHint=false, destructiveHint=false), the description adds useful behavioral details: the ticket expires in 1 hour, the upload requires matching Content-Type, and the returned r2Path is used in place of imageUrl. No contradictions with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each earning its place: the local-file use case, the exact upload workflow, and the expiration caveat. The key differentiator (LOCAL) is front-loaded and the instructions are immediately actionable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description compensates by naming the critical return fields (uploadUrl, r2Path) and explaining how to use them. It also covers the lifecycle (1-hour expiry), the required PUT behavior, and the integration with generation tools—everything an agent needs to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so filename, sizeBytes, and contentType are already documented. The description reinforces the 'same Content-Type' requirement, which is helpful context for using contentType, but it doesn't add substantial meaning beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get a presigned upload URL for a LOCAL image file.' It also distinguishes it from the URL-upload sibling by calling out 'the one case a URL can't cover,' and names the relevant output fields (uploadUrl, r2Path) so an agent immediately knows what this tool produces.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit use context: this is for LOCAL files, not URLs, and it gives a step-by-step flow (PUT to uploadUrl with same Content-Type, then pass r2Path to a generation tool). It stops short of naming the sibling tool upload_image_from_url as the alternative, but the 'URL can't cover' phrase effectively routes the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
day_to_nightDay to NightInspect
Day to dusk (virtual twilight): turn a daytime listing photo into a magazine-style evening scene — lights on, warm glow, dusk sky — with the building and camera angle unchanged. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
declutter_photoDeclutterInspect
Remove clutter, mess, and personal items from a listing photo while keeping the room, furniture, and architecture intact. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
draw_floor_planDraw Floor PlanInspect
Free (no credits): draw a clean 2D floor plan from a layout YOU write — read the user's description, or look at their hand sketch or brochure plan, and send every room as a rectangle in metres (or feet) plus doors and windows. Returns the drawn plan (areas and dimensions on it) at once, saved so the user can fine-tune it in Pixly's floor plan editor. If the layout has problems (overlapping rooms, a door between rooms that don't touch) you get exactly what to fix — fix it and call again. To change a plan, call again with its planId and the whole updated layout; the new version is saved as its own plan and the earlier one is kept.
| Name | Required | Description | Default |
|---|---|---|---|
| doors | No | ||
| rooms | Yes | Every room as an axis-aligned rectangle. Neighbouring rooms must share the wall exactly (one's right edge = the other's left edge) and must not overlap. An L-shaped space = two rectangles joined by a doorway. Lay out a typical sensible plan when the user gives only rough sizes. | |
| title | No | Address or listing name for the plan's title block. | |
| units | No | Units of every number below, and of the labels on the plan. | m |
| planId | No | To CHANGE a plan you drew before: its planId from that result, with the whole updated layout — saved as a new plan beside it (nothing is overwritten). Omit for a new plan. | |
| windows | No | ||
| 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. |
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 |
edit_staged_photoEdit PhotoInspect
Change one thing in a photo and keep everything else exactly as it is — the parts the edit doesn't touch are copied from the photo, not redrawn. Works on any photo: a staged room, any Pixly result, or the user's own picture (swap the sofa, recolour a wall, remove a car, change the words on a sign). Optional mask limits the change to a marked area. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| mask | No | Optional area to change: a PNG as a data:image/png;base64 URI or an https URL, the photo's shape, WHITE where the photo may change and BLACK (or transparent) everywhere else. Leave it out to let the request alone decide — that already keeps the rest of the photo. | |
| style | No | Optional. Style id of the staging being edited (the ids virtual_staging takes). Left out, it is read from the photo's history; a photo that was never staged needs none. | |
| r2Path | No | Storage path of the photo to edit (a resultPaths entry, or an upload) — the alternative to imageUrl. | |
| imageUrl | No | The photo to edit: a Pixly result (a resultUrls entry), the user's own photo, or any public image URL / data:image URI. Either imageUrl or r2Path is required. | |
| 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. | |
| maskR2Path | No | Storage path of a mask — the alternative to mask. | |
| sourceJobId | No | Job the photo came from, when it is a Pixly result (lineage) | |
| sourceResultIndex | No | Which of that job's results was edited | |
| customInstructions | Yes | The change to make, in the user's words, e.g. "make the sofa dark green", "remove the car from the driveway", "change the sign to SOLD". |
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 |
enhance_photoEnhanceInspect
Real estate photo editing in one step: turn an amateur listing photo into a finished, professional photo (exposure, color, clarity). Returns 3 variants to pick from. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
flythrough_videoFlythroughInspect
Flythrough video: one continuous camera move through a home from 2-4 room photos in walking order. Each pair of neighbouring photos becomes a 3-second move that flies from one room into the next, and the moves are stitched into one film with a cinematic speed ramp. Returns one job: poll get_job until the film is ready (a few minutes). Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Optional name for the tour, e.g. the street address. | |
| format | No | Film shape. Omit to follow the photos (landscape photos → 16:9). | |
| photos | Yes | The rooms in walking order, 2 to 4 photos (e.g. hallway → living room → kitchen). Each photo should show the doorway or opening into the next room — the camera flies through it. Each item takes imageUrl or r2Path. | |
| 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. |
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 |
get_checkout_linkGet a Payment LinkAInspect
Use when a tool fails for lack of credits or a plan. Returns a Stripe Checkout URL for the user to pay on — this never charges anything by itself, and you cannot pay for them. With no active plan it is a subscription (plans: starter (Starter: $5.99/week, 20 credits); agent (Agent: $19.99/month, 100 credits); pro_agent (Pro Agent: $49.99/month, 300 credits); team (Team: $149.99/month, 1000 credits)); with a plan it is a one-time credit top-up. After they pay, credits arrive in seconds: check get_credit_balance, then run the tool again.
| Name | Required | Description | Default |
|---|---|---|---|
| plan | No | Plan to subscribe to, for an account with no active plan. Defaults to "starter". Ignored for a top-up. | |
| topUpUsd | No | For an account that already has a plan: one-time credit top-up amount in USD (10–500, default 10), priced at that plan's rate. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses key behaviors beyond the sparse annotations: 'this never charges anything by itself', 'you cannot pay for them', and credits arrive in seconds after payment. It also explains the state-dependent behavior (subscription vs. top-up), adding significant value beyond the readOnlyHint/destructiveHint flags.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense but every sentence earns its place: the usage trigger is front-loaded, then behavioral details and state-dependent logic are covered, and it ends with a clear follow-up. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description explains what is returned (a Stripe Checkout URL), the payment flow, the two state-dependent behaviors, and the recommended next steps. An agent has all necessary information to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Although the schema already has 100% coverage, the description adds critical meaning: plan pricing and credit counts, that the 'plan' parameter is ignored for top-ups, and that topUpUsd only applies to accounts with an existing plan. This exceeds what the schema alone provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns a Stripe Checkout URL and specifies the trigger condition ('when a tool fails for lack of credits or a plan'). It distinguishes itself from the sibling get_credit_balance by focusing on generating a payment link rather than checking balance.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says when to use the tool, defines behavior for both scenarios (no active plan vs. active plan), and provides a clear follow-up sequence ('check get_credit_balance, then run the tool again'). It also notes the agent cannot pay on the user's behalf, which is a critical usage constraint.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_credit_balanceCredit BalanceARead-onlyInspect
The user's current Pixly credit balance and plan.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the useful context that the balance is 'current' and tied to the authenticated user, but does not disclose any additional behavior such as return format or potential errors. With annotations providing the main behavioral safety, a mid-range score is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no wasted words. It front-loads the key information (credit balance and plan) and avoids any redundant detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only tool with no parameters and no output schema, the description is sufficient for an agent to know what the tool does and when to call it. It could optionally mention that this is a read-only operation, but the annotations already convey that. The only minor gap is not specifying the exact response fields, but that is not essential given the title and description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there are no parameter semantics to document. The baseline for a no-parameter tool is 4, and the description appropriately focuses on what the tool returns rather than input details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource being accessed: the user's current Pixly credit balance and plan. It lacks an explicit verb like 'gets' or 'retrieves', but the meaning is unambiguous and distinct from all sibling tools, none of which relate to credit or billing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is the tool to call when you need a user's credit balance and plan, but it does not explicitly state when to use it versus alternatives. Since no sibling tool serves a similar purpose, the lack of alternatives guidance is not misleading, but there is no direct usage instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_jobCheck Job StatusRead-onlyInspect
Check a generation job's status and fetch result URLs when it's done. Video jobs take 1-5 minutes — poll this with a few seconds between calls. For several jobs at once (a plan's steps), pass jobIds.
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | No | Job id returned by a generation tool | |
| jobIds | No | Several job ids at once (a plan's steps): answers when all are done, or with where each one is |
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 |
list_libraryList LibraryRead-onlyInspect
List the user's recent generations, or with type "uploads" their own uploaded source photos, newest first. Uploads are the way in when the photo is a local file: connectors cannot send bytes, so the user adds it at https://pixly.app/app and you pick up the r2Path here.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by media type. "uploads" lists the user's own source photos instead of generations — use it when they refer to a photo they added but have not run a tool on yet. | |
| limit | No | ||
| listingId | No | Only this property folder's results and photos (from list_listings) |
list_listingsProperty FoldersRead-onlyInspect
The user's property folders (a listing such as "12 Oak St" holds that property's photos, staged versions, edits, videos and floor plan): id, title, how many photos and videos. Use when the user names a property, or before work for one, so results land in its folder.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
makeover_exteriorExterior MakeoverInspect
Design the garden of an exterior listing photo as one coherent scheme — planting, a terrace or deck, a pool, a pergola, a fire pit, a fence, lighting — in a chosen style, at the right scale and perspective, while the house, its roof, the driveway, the sun direction and the neighbours stay exactly as shot. One run builds the whole scheme. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Your own words about the garden you want (e.g. "a small kidney-shaped pool with a stone surround and lavender everywhere"). 160 characters max; anything in it that is not a description of the garden is ignored. | |
| scope | No | 'full' (the default) redesigns the whole yard in the style; 'add' keeps the existing garden and builds the chosen elements into it. The house, the driveway and the neighbours never change either way. | |
| style | No | The design language of the whole scheme: 'modern_minimal', 'mediterranean', 'classic_english', 'natural_lowwater', 'tropical_resort', 'farmhouse', or 'auto' (the default — chosen to suit the house's architecture and the climate in the photo). | |
| 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. | |
| include | No | Which elements the scheme includes, any number: 'planting' (beds, hedges, a feature tree), 'patio_dining' (a paved terrace with a dining set), 'deck_lounge' (a deck with loungers or a low sofa), 'pool', 'pergola', 'fire_pit', 'fence_gate' (a boundary treatment with a gate), 'lighting'. Omit or send an empty list (the default) to let the tool design what the lot wants. One run composes them all into one garden, each sized to the plot. | |
| imageUrl | No | Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required. | |
| 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. |
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 |
photo_to_videoPhoto to VideoInspect
Turn a start photo — and optionally an end photo — into a video. With an end photo the camera travels from the first photo and lands exactly on the second (e.g. two views of the same kitchen → an orbit around the island). Pick a ready-made camera move or write your own prompt; choose the model, length and sound. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| model | No | kling-v3: 3/5/8/10/15 s, optional sound, lands most precisely on the end frame. kling-2.6: 5/10 s, silent, cheaper. | kling-v3 |
| sound | No | Add ambient sound (kling-v3 only; kling-2.6 is always silent). | |
| format | No | Video shape. original (default) keeps the start photo's own shape; 16:9, 9:16 or 1:1 crop the photos, centred, to that shape before they are animated. | original |
| prompt | No | Your own description of the video, in any language. Replaces cameraMove when set. | |
| 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 | Start frame — where the video begins. Public https URL or data: URI; either imageUrl or r2Path is required. | |
| endR2Path | No | R2 path of the end frame — the alternative to endImageUrl. | |
| 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. | |
| cameraMove | No | Ready-made camera move used when no prompt is given. | smooth |
| endImageUrl | No | Optional end frame — the camera travels from the start photo and lands exactly on this one. Best when both photos show the same space from different spots. | |
| durationSeconds | No | Clip length. kling-v3 takes 3, 5, 8, 10 or 15; kling-2.6 takes 5 or 10. |
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 |
plan_photosPlan Photo EditsInspect
Several listing photos at once: one plan of photo steps (straighten, enhance, sky, lawn, staging, declutter…) with one total and one confirmation, instead of a confirm per photo. The first call runs nothing: it returns each step's cost, the total and a confirmationCode, and the Pixly card shows the plan with one button. After the user says yes in the chat, call again with only confirmationCode: it starts every step whose photo is ready and returns their jobs (poll with get_job jobIds). Steps that work on an earlier step's result start when you call again with the same confirmationCode once that result is completed. Only for photos; videos have their own tools.
| Name | Required | Description | Default |
|---|---|---|---|
| steps | No | What to do, step by step | |
| photos | No | Every photo of the set, in order; steps refer to them by number (from 1) | |
| 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. | |
| confirmationCode | No | The plan's confirmationCode — only after the user agreed to the plan. Starts the steps whose photo is ready; call again with it later to start steps that work on earlier results. |
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 |
plot_signPlot NumberInspect
Place a photorealistic 3D monument sign with your exact text (price, area, SOLD) onto a photo of an empty plot, matched to perspective and lighting. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| look | No | Sign material/style; defaults server-side | |
| text | Yes | Sign label, verbatim — a price ("$1,200,000"), area ("800 m²"), or short word ("SOLD") | |
| 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. | |
| 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. | |
| orientation | No | Letter orientation (letter looks only); defaults server-side |
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 |
remove_furnitureRemove FurnitureInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
render_floor_planFloor Plan RenderInspect
Turn a picture of any floor plan — a hand sketch, a photo of a brochure page, a blueprint, a screenshot — into a polished real-estate floor plan: a furnished top-down 2D plan with real floors and room names, or a 3D isometric cutaway. The rooms, walls, doors and windows are kept exactly as drawn; nothing is added and written dimensions are left off. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| look | No | Which picture to make of the plan: 'furnished' (the default — a polished top-down 2D plan with real floors, furniture and room names) or 'isometric' (a 3D cutaway of the same layout, furnished, no text). The photo must show a floor plan: a hand sketch, a brochure page, a blueprint, a screenshot. The layout is kept exactly as drawn; written dimensions are left off. | |
| 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. | |
| 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. |
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 |
replace_lawnLawn ReplacementInspect
Turn patchy, brown or bare grass in an exterior listing photo into a healthy green lawn, leaving driveways, paths, beds and the house untouched. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| lawn | No | Lawn style. 'auto' lets the tool pick a healthy lawn that suits the photo. | auto |
| shade | No | How green; only used with a chosen lawn style. | medium |
| 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. | |
| stripes | No | Mowing stripes: auto (stripes for fresh_mown and golf, none otherwise), on, off. | auto |
| imageUrl | No | Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required. | |
| 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. |
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 |
replace_skySky ReplacementInspect
Replace a grey, overcast or blown-out sky in an exterior listing photo with a natural clear blue sky, matching the light and keeping the building, trees and reflections unchanged. A run takes about 1–2 minutes; poll get_job until it completes. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| sky | No | Sky style. 'auto' lets the tool pick what suits the photo's light. | auto |
| sun | No | Sun glow: auto (a glow for sunset/sunrise styles, none otherwise), on (place it with sunX/sunY), off. | auto |
| sunX | No | With sun=on: glow position from the left edge, 0..1. | |
| sunY | No | With sun=on: glow position from the top edge, 0..1 (kept in the top 60%). | |
| 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. | |
| 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. |
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 |
reset_seasonSeasonal ResetInspect
Photograph the same property in another season: take the snow off the ground, the roof and the branches and put the garden in leaf, or move a summer shot to autumn or winter. The house, the driveway, the paths and the camera angle stay exactly as shot. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| season | No | The season to show the property in: 'spring', 'summer', 'autumn', 'winter', or 'auto' (the default — the tool shows the property at its best, which for a snowy or dormant photo means high summer). Only the planting, the ground cover and the daylight change; the house, the driveway, the paths and the framing stay exactly as shot. | |
| imageUrl | No | Public https URL of the source photo, or a data: URI. Either imageUrl or r2Path is required. | |
| 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. |
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 |
restyle_roomRestyleInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| 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 |
straighten_photoStraighten PhotoInspect
Free (no credits): automatically straighten a property photo — leaning walls made vertical (converging verticals from a tilted camera) and a tilted horizon levelled, like a pro photographer's lens correction. Crops the edges slightly. Best before staging or any other edit. Says so when the photo is already straight or has no straight lines to go by.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
touch_up_exteriorExterior Touch-upInspect
One-click retouch of an exterior listing photo: a natural sky where it is dull, a healthy lawn where the grass is dead, a clean driveway, and bins, hoses and other clutter removed — each only where needed, with the house unchanged. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| fix | No | Which areas the tool may touch: 'sky', 'lawn', 'hardscape' (driveway, paths, patio), 'clutter' (bins, hoses, tools, a stray vehicle). Omit for all four; each is fixed only where the photo needs it. | |
| 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. | |
| 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. |
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 |
update_listingRename Property FolderInspect
Rename one of the user's property folders, only when they ask.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Its new name | |
| listingId | Yes | The folder (from list_listings) |
upload_image_from_urlImport Photo from URLAInspect
Rarely needed: generation tools take an imageUrl directly. Use this only to import a photo into Pixly ahead of time, e.g. to reuse one URL across several tools without refetching it each time.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Publicly reachable image URL (JPG/PNG/WebP, max 10 MB) to import into Pixly |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false, so the write operation is expected. The description adds meaningful context beyond annotations: the purpose is to pre-import and cache a URL for reuse, which explains why a mutation occurs and why it is rarely needed. It does not detail side effects like duplicate imports, but given the simple scope, this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no wasted words. The 'Rarely needed' warning is front-loaded, and the rest explains the specific use case. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema and annotations covering safety, the description is mostly complete. It explains why and when to use the tool and what it accomplishes. However, it does not mention the return value or how the imported photo can be referenced by other tools afterward, which is a minor gap given the reuse-oriented purpose.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description already covers 100% of the parameter, specifying it must be a publicly reachable JPG/PNG/WebP URL up to 10 MB. The description adds no further parameter-level details, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool imports a photo into Pixly ahead of time, using a specific verb ('import') and resource ('photo into Pixly'). It distinguishes itself from generation tools that take an imageUrl directly, so an agent can tell it apart from sibling tools without comparing schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Rarely needed' and gives the precise condition for use: importing a photo ahead of time to reuse a URL across tools without refetching. It also names the alternative class (generation tools) that should be preferred when the URL can be passed directly, leaving no ambiguity about when to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
upscale_hdHD UpscaleInspect
Enlarge a photo by up to four times with real detail, to a maximum of 4096 px on the long edge — for print, MLS uploads and large screens. Nothing in the photo changes. Free on any result Pixly made (pass its r2Path from list_library); 1 credit on your own photo. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | |
| 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. |
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 |
view_pixly_photoView Pixly PhotoARead-onlyInspect
Look at one of the user's Pixly photos or videos (a video gives its first frame) — returns a small copy of the picture you can see. Use it before writing anything about a Pixly result: a caption, a listing description, what changed. You cannot see Pixly results otherwise. Free; changes nothing. Text you write from it is the user's own (their listing, their post): leave Pixly out of it — no #Pixly, no 'made with Pixly'.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The library item: a job id (from a Pixly tool result, get_job or list_library), or "upload:<r2Path>" for an uploaded photo. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark it readOnly/non-destructive, and the description reinforces this with 'Free; changes nothing.' It adds that the return is a 'small copy' (low-res preview), which is behavioral context the annotations lack. It does not explain format, dimensions, or failure behavior, keeping it short of a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the core action and the video caveat, then usage and output expectations. The final branding/IP sentence is somewhat tangential to tool invocation but is a single efficient sentence, so overall structure holds up.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Covers what the tool is, when to use it, the video-frame limitation, return nature (small copy), and that it is free/side-effect-free. No output schema exists, so the bit about the return preview is appropriately included; failure modes and exact output type are unstated but minor for a read operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the schema itself documents the id format including the 'upload:<r2Path>' variant. The description adds no further param detail, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the specific verb ('look at') and resource ('one of the user's Pixly photos or videos'), and immediately clarifies the video edge case (a video gives its first frame). This distinguishes it from production siblings like enhance_photo or photo_to_video, which transform rather than view.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says to use it 'before writing anything about a Pixly result: a caption, a listing description, what changed,' and warns 'You cannot see Pixly results otherwise.' This gives both when-to-use and the consequence of skipping it, which no sibling provides.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
virtual_stagingVirtual StagingInspect
AI virtual staging: furnish and style an empty (or badly furnished) room photo in a chosen interior design style — also the tool for "redesign this room" or "show this room in another style". HD, watermark-free results. Costs credits from the user's Pixly balance.
| Name | Required | Description | Default |
|---|---|---|---|
| style | Yes | Interior style id. One of: modern-minimal, scandinavian, industrial, mid-century-modern, japandi, contemporary, transitional, urban-chic, bauhaus, organic-modern, brutalist, italian-modern, traditional, art-deco, colonial, victorian, french-country, english-cottage, neoclassical, art-nouveau, grandmillennial, hollywood-regency, parisian-chic, modern-classic, craftsman, mediterranean, mediterranean-modern, rustic-farmhouse, bohemian, tropical, family-staging, hygge, wabi-sabi, modern-farmhouse, cottagecore, shabby-chic, cabin-lodge, eclectic, retro-70s, warm-luxury, investor-premium, contemporary-dark, glam, penthouse-modern, hotel-suite, maximalist, quiet-luxury, coastal, desert-modern, hacienda, pacific-northwest, caribbean-resort, hamptons, moroccan, tuscan, southwestern, asian-zen, coastal-grandmother, cape-cod, california-casual, mountain-modern. When the user has no preference, "modern-minimal" or "scandinavian" suit most listings. | |
| 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. | |
| roomType | No | Room type hint; omit to let vision infer it from the photo | |
| 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. | |
| numImages | No | Ignored — staging always returns one image. Call again for another take. | |
| stagingQuality | No | Ignored — the Pro tier is retired. Every staging costs 1 credit. | |
| customInstructions | No | Optional: ONLY a wish the user stated beyond the style and room, in their words (e.g. "add a reading chair", "no rug"). Leave it out otherwise — Pixly writes the staging prompt itself (keeps walls, windows and camera angle, furnishes to scale); never restate the request or list furniture here. |
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 |
watermark_photosWatermark PhotosInspect
Free (no credits): put the agent's or agency's mark on listing photos — text (name, phone) and/or the logo saved on their Pixly account — in a corner or the middle, up to 10 photos per call. Returns every marked photo at once.
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | medium | |
| text | No | The text, e.g. "Smith Realty · 555-0100". Optional when the account has a saved logo. | |
| photos | Yes | The photos to mark, 1–10. Each item takes imageUrl or r2Path. | |
| useLogo | No | Add the logo saved on the account (Pixly floor plan settings), when there is one. | |
| position | No | bottom-right | |
| 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. |
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 |
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
30 tool updates
- Changed
before_after_image2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
before_after_reel2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
blur_faces_plates2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
cinematic_motion2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Added
create_listing - Changed
day_to_night2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
declutter_photo2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
draw_floor_plan2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
edit_staged_photo2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
enhance_photo2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
flythrough_video2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
get_job3 fields changed- added
Input schema / properties / jobIdsAdded value: +{ + "description": "Several job ids at once (a plan's steps): answers when all are done, or with where each one is", + "items": { + "minLength": 1, + "type": "string" + }, + "maxItems": 20, + "minItems": 1, + "type": "array" +} - removed
Input schema / requiredRemoved value: -[ - "jobId" -] - added
Output schema / properties / jobsAdded 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" +}
- Changed
list_library1 field changed- added
Input schema / properties / listingIdAdded value: +{ + "description": "Only this property folder's results and photos (from list_listings)", + "type": "string" +}
- Added
list_listings - Changed
makeover_exterior2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
photo_to_video2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Added
plan_photos - Changed
plot_sign2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
remove_furniture2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
render_floor_plan2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
replace_lawn2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
replace_sky2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
reset_season2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
restyle_room2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
straighten_photo2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
touch_up_exterior2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Added
update_listing - Changed
upscale_hd2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
virtual_staging2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
- Changed
watermark_photos2 fields changed- added
Input schema / properties / listingIdAdded 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" +} - added
Output schema / properties / jobsAdded 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" +}
1 tool update
- Changed
virtual_staging1 field changed- changed
Input schema / properties / customInstructions / descriptionPrevious value: -"Optional extra instructions blended into the staging prompt"New value: +"Optional: ONLY a wish the user stated beyond the style and room, in their words (e.g. \"add a reading chair\", \"no rug\"). Leave it out otherwise — Pixly writes the staging prompt itself (keeps walls, windows and camera angle, furnishes to scale); never restate the request or list furniture here."
3 tool updates
- Changed
before_after_reel3 fields changed- changed
Input schema / properties / format / defaultPrevious value: -"9:16"New value: +"original" - added
Input schema / properties / format / descriptionAdded value: +"Video shape. original (default) keeps the photos' own shape; 9:16, 16:9 or 1:1 crop both photos, centred, to that shape first." - changed
Input schema / properties / format / enumPrevious value: -[ - "9:16", - "16:9", - "1:1" -]New value: +[ + "original", + "9:16", + "16:9", + "1:1" +]
- Changed
cinematic_motion3 fields changed- changed
Input schema / properties / format / defaultPrevious value: -"9:16"New value: +"original" - changed
Input schema / properties / format / descriptionPrevious value: -"Aspect ratio"New value: +"Video shape. original (default) keeps the photo's own shape; 9:16 or 16:9 crop the photo, centred, to that shape before it is animated." - changed
Input schema / properties / format / enumPrevious value: -[ - "9:16", - "16:9" -]New value: +[ + "original", + "9:16", + "16:9" +]
- Changed
photo_to_video3 fields changed- changed
Input schema / properties / format / defaultPrevious value: -"16:9"New value: +"original" - changed
Input schema / properties / format / descriptionPrevious value: -"Label for the clip's shape; the video follows the start photo's own shape."New value: +"Video shape. original (default) keeps the start photo's own shape; 16:9, 9:16 or 1:1 crop the photos, centred, to that shape before they are animated." - changed
Input schema / properties / format / enumPrevious value: -[ - "16:9", - "9:16", - "1:1" -]New value: +[ + "original", + "16:9", + "9:16", + "1:1" +]
25 tool updates
- Changed
before_after_image1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
before_after_reel1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
blur_faces_plates1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
cinematic_motion2 fields changed- changed
Input schema / properties / durationSeconds / descriptionPrevious value: -"Clip length; the routed model validates its supported tiers"New value: +"Clip length in seconds. Leave out for the default 5 s; 10 s costs about twice as much — use it only when the user asks for a longer video." - added
Output schema / properties / quoteAdded 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" +}
- Changed
day_to_night1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
declutter_photo1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
draw_floor_plan1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
edit_staged_photo1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
enhance_photo1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
flythrough_video1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
get_job1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
makeover_exterior1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
photo_to_video1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
plot_sign1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
remove_furniture1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
render_floor_plan1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
replace_lawn1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
replace_sky1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
reset_season1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
restyle_room1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
straighten_photo1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
touch_up_exterior1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
upscale_hd1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
virtual_staging1 field changed- added
Output schema / properties / quoteAdded 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" +}
- Changed
watermark_photos1 field changed- added
Output schema / properties / quoteAdded 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" +}
1 tool update
- Changed
restyle_room2 fields changed- changed
Input schema / properties / looks / descriptionPrevious 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." - changed
Input schema / properties / surfaces / descriptionPrevious 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."
1 tool update
- Changed
restyle_room4 fields changed- changed
Input schema / properties / colours / descriptionPrevious 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." - changed
Input schema / properties / looks / additionalProperties / enumPrevious 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" +] - changed
Input schema / properties / looks / descriptionPrevious 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." - added
Input schema / properties / referencesAdded 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" +}
1 tool update
- Changed
edit_staged_photo10 fields changed- changed
Input schema / properties / customInstructions / descriptionPrevious value: -"The concrete edit to apply, e.g. \"change the sofa to grey\""New value: +"The change to make, in the user's words, e.g. \"make the sofa dark green\", \"remove the car from the driveway\", \"change the sign to SOLD\"." - changed
Input schema / properties / imageUrl / descriptionPrevious value: -"URL of the PREVIOUS staged result to edit (the resultUrls entry from its job). Either imageUrl or r2Path is required."New value: +"The photo to edit: a Pixly result (a resultUrls entry), the user's own photo, or any public image URL / data:image URI. Either imageUrl or r2Path is required." - added
Input schema / properties / maskAdded value: +{ + "description": "Optional area to change: a PNG as a data:image/png;base64 URI or an https URL, the photo's shape, WHITE where the photo may change and BLACK (or transparent) everywhere else. Leave it out to let the request alone decide — that already keeps the rest of the photo.", + "minLength": 1, + "type": "string" +} - added
Input schema / properties / maskR2PathAdded value: +{ + "description": "Storage path of a mask — the alternative to mask.", + "minLength": 1, + "type": "string" +} - changed
Input schema / properties / r2Path / descriptionPrevious value: -"R2 path of the previous staged result — the alternative to imageUrl."New value: +"Storage path of the photo to edit (a resultPaths entry, or an upload) — the alternative to imageUrl." - changed
Input schema / properties / sourceJobId / descriptionPrevious value: -"Job the edited result came from (lineage)"New value: +"Job the photo came from, when it is a Pixly result (lineage)" - changed
Input schema / properties / sourceResultIndex / descriptionPrevious value: -"Which variation was edited"New value: +"Which of that job's results was edited" - changed
Input schema / properties / style / descriptionPrevious value: -"Style id of the staging being edited (the same ids virtual_staging takes), used as context to match new elements"New value: +"Optional. Style id of the staging being edited (the ids virtual_staging takes). Left out, it is read from the photo's history; a photo that was never staged needs none." - removed
Input schema / properties / style / minLengthRemoved value: -1 - changed
Input schema / requiredPrevious value: -[ - "style", - "customInstructions" -]New value: +[ + "customInstructions" +]
1 tool update
- Changed
restyle_room3 fields changed- added
Input schema / properties / coloursAdded 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" +} - changed
Input schema / properties / looks / additionalProperties / enumPrevious 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" +] - changed
Input schema / properties / looks / descriptionPrevious 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."
1 tool update
- Changed
virtual_staging1 field changed- changed
Input schema / properties / stagingQuality / descriptionPrevious value: -"Ignored — the Pro tier is retired. Every staging costs 1 credit and may render a second version on another model for free."New value: +"Ignored — the Pro tier is retired. Every staging costs 1 credit."
1 tool update
- Changed
draw_floor_plan1 field changed- changed
Input schema / properties / planId / descriptionPrevious value: -"To CHANGE a plan you drew before: its planId from that result, with the whole updated layout. Omit for a new plan."New value: +"To CHANGE a plan you drew before: its planId from that result, with the whole updated layout — saved as a new plan beside it (nothing is overwritten). Omit for a new plan."
25 tool updates
- Changed
before_after_image1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
before_after_reel1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
blur_faces_plates1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
cinematic_motion1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
day_to_night1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
declutter_photo1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
draw_floor_plan1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
edit_staged_photo1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
enhance_photo1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
flythrough_video1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
get_job1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
makeover_exterior1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
photo_to_video1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
plot_sign1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
remove_furniture1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
render_floor_plan1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
replace_lawn1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
replace_sky1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
reset_season1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
restyle_room1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
straighten_photo1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
touch_up_exterior1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
upscale_hd1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
virtual_staging1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
- Changed
watermark_photos1 field changed- added
Output schema / properties / resultPathsAdded 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" +}
1 tool update
- Changed
draw_floor_plan11 fields changed- removed
Input schema / properties / doors / items / properties / width / exclusiveMinimumRemoved value: -0 - added
Input schema / properties / doors / items / properties / width / minimumAdded value: +0.1 - removed
Input schema / properties / planId / formatRemoved value: -"uuid" - added
Input schema / properties / planId / maxLengthAdded value: +40 - removed
Input schema / properties / planId / patternRemoved value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$" - removed
Input schema / properties / rooms / items / properties / depth / exclusiveMinimumRemoved value: -0 - added
Input schema / properties / rooms / items / properties / depth / minimumAdded value: +0.1 - removed
Input schema / properties / rooms / items / properties / width / exclusiveMinimumRemoved value: -0 - added
Input schema / properties / rooms / items / properties / width / minimumAdded value: +0.1 - removed
Input schema / properties / windows / items / properties / width / exclusiveMinimumRemoved value: -0 - added
Input schema / properties / windows / items / properties / width / minimumAdded value: +0.1
1 tool update
- Added
blur_faces_plates
1 tool update
- Added
watermark_photos
3 tool updates
- Added
draw_floor_plan - Added
straighten_photo - Added
view_pixly_photo
1 tool update
- Added
before_after_image
1 tool update
- Added
flythrough_video
Related MCP Connectors
Enhance, virtually stage and turn real estate listing photos into video with AI.
AI virtual staging for real estate — stage rooms, beautify floor plans, classify images.
- Archome AIOAuthai.archome
AI virtual staging and architectural rendering: stage rooms, render interiors, exteriors, sketches.
AI image, video and audio generation for agents: banners, reveal videos, avatars, voice cloning.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAI-powered virtual staging for real estate professionals: stage empty rooms with photorealistic furniture, beautify floor plans into 3D renders, classify rooms, generate German property descriptions, and get style recommendations.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI assistants with real-estate visual tools including virtual staging, photo enhancement, decluttering, day-to-night conversion, plot signs, and cinematic property videos via the Pixly API.69 npmMIT

Luw MCP Serverofficial
AlicenseAqualityCmaintenanceEnables AI-driven interior, exterior, and landscape design, photoreal rendering, image editing, video generation, and 3D model creation directly inside Claude, Cursor, VS Code, and other MCP clients. It also supports virtual staging, sketching to render, texture and pattern generation, background removal, and architectural consultation through natural language.2449 npmMIT
Hermosoofficial
AlicenseBqualityBmaintenanceMarketing on autopilot from any AI agent, 900+ tools. Research winning ads across ad libraries and organic social, make image and video ads with your real product, batch static ads from a product catalog, swap a real or AI presenter into any video, publish to 10 social channels or let Autopilot posting fill your calendar, automate DMs, and run campaigns on 12 ad platforms.1853,383 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.