← Plugin catalog
Creativity

Product Photos by RunComfy

Inceptions AI INC v1.0.2

Create studio and scene photos

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Create clean product photos
  • Stage product lifestyle scenes
  • Create product image variants

Declared limitations

  • N1: planning is not generation.
  • N2: generative editing cannot guarantee a pixel-identical alpha cutout.
  • N3: private local media may not be published silently.

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Help me turn a product photo into a clean studio image; explain which image link you need.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.

View package source →

Description

From the marketplace listing

Product Photos by RunComfy turns existing product photos into clean studio images, lifestyle scenes and campaign variants using compatible image models. What you can do: - Create a clean product image with a white or studio background. - Place a product into a described lifestyle setting. - Prepare a requested set of images for different scenes or formats. - Define the product color, shape, label and material details to check against the original. Connect a RunComfy account to generate images. Generations use your RunComfy account balance. Model choices and available dimensions depend on the current catalog. Provide a product photo through an accessible HTTPS link. The plugin asks for a usable link if a chat attachment cannot be passed to the model. AI edits can change labels, geometry and fine details, so compare every result with the original before commercial use. A white background does not imply a transparent cutout. The plugin does not automatically publish images to an online store.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 18, 2026. Last seen Nov 18, 2026.

Similar plugins

Similar plugins could not be prepared right now. Please try again in a moment.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package7 files · 21.1 KBBrowse files →
Skill instructions
clean-product-photo8.66 KB

View saved version →

---
name: clean-product-photo
description: Improve a user-supplied product photo with RunComfy, such as a cleaner studio background, lighting or minor visual cleanup. Requires an accessible source photo; does not provide exact product preservation or transparent cutouts.
---

# Clean a product photo

Use this plugin's RunComfy MCP tools to make the requested edit to the actual supplied product image. Respond in the user's language. This skill requires no CLI, external skill or assumed uploader.

Use only this plugin’s current host-provided tool definitions: actual names, descriptions, typed outer arguments and allowed model scope. If current definitions cannot be verified, report an unverified connection binding, not that RunComfy lacks the product capability. If verified definitions offer no compatible operation, explain the connection-specific limitation before spending. Do not assume a discovery tool, switch endpoints, invent operations or bypass the connection through workflow/deployment execution.

## Establish the product and permitted change

Record a short product checklist from the supplied image, then use the requested destination—such as a listing hero, catalog card or ad—to choose supported framing and dimensions. Do not infer marketplace requirements or certify compliance. The deliverable is the requested cleanup plus a source-to-result check of product details and any verifiable output format.

Use the supplied product/SKU reference to record the intended item, variant/color, material, visible label/logo/text, silhouette and important components. A filename or SKU string alone does not establish what an unseen product looks like. Ask about an ambiguity only when it affects which product or feature must be retained.

Separate the requested cleanup from product attributes: for example, change the background or reduce a distracting reflection while aiming to retain the bottle, cap, label and amber color. Do not silently remove a logo or physical component as a blemish, recolor the item, substitute a similar SKU, or recreate an unavailable source from a text guess. Product identifiers guide the task; do not invent a `sku` model input property.

Treat preservation as a goal to check, not a guarantee. This generative workflow can redraw labels, geometry and color. If the user needs exact packaging text, calibrated color or pixel-identical product pixels, explain the limitation before a paid edit. A white background is not transparency: do not promise an alpha cutout, invent a mask parameter or call a white JPEG a transparent PNG.

## Source photo and exposed operation

For reference media, use externally fetchable HTTPS URLs that an unauthenticated GET can retrieve. When the host supplies such a URL for the user’s attachment and access is authorized for this task, use it directly; do not request another upload. Local paths, `file://`, internal attachment/sandbox IDs and data URIs cannot be passed to the Model API. Without a usable URL, explain the limit and request a direct link or a genuinely available, authorized host upload. These MCP tools do not upload arbitrary media: do not invent hosting, publish private media without permission, embed account credentials in URLs or repurpose training uploads.

Before a paid call, confirm each reference is a supported still image from reliable supplied metadata or an available inspection feature. A known HTML/login/model page, video or audio URL is not an image input merely because it is HTTPS or returns 200. If the media type is inaccessible or ambiguous, resolve it or request a direct supported image URL before a paid generation; do not claim a check you could not perform or invent an upload/conversion.

1. Select a currently exposed image operation that supports the actual source/reference images and requested edit or composition. Use `generate_image` when the current host exposes a compatible definition, following its actual declared arguments and allowed model scope. A tex

Preview of the first 4,000 characters. Read full instructions →

product-asset-variants8.93 KB

View saved version →

---
name: product-asset-variants
description: Generate a bounded set of product-image composition or aspect-ratio variants from supplied product references with RunComfy. Use for requested campaign assets; generated variants may redraw details and are not lossless resizing or guaranteed identical SKUs.
---

# Product asset variants

Create only the campaign variants the user requested using this plugin's RunComfy MCP tools. Respond in the user's language. This skill does not depend on a CLI, another skill, an uploader or an exact image-resizing service.

Use only this plugin’s current host-provided tool definitions: actual names, descriptions, typed outer arguments and allowed model scope. If current definitions cannot be verified, report an unverified connection binding, not that RunComfy lacks the product capability. If verified definitions offer no compatible operation, explain the connection-specific limitation before spending. Do not assume a discovery tool, switch endpoints, invent operations or bypass the connection through workflow/deployment execution.

## Define the variant matrix

For each requested asset, include its intended channel or placement when supplied, supported format/ratio, product details to retain and allowed scene changes. This is a bounded campaign deliverable, not an automatic store integration: label each result against its row and distinguish verified format/product checks from unresolved ones.

List each requested output as a row with its intended product/SKU, real source reference, color/variant, scene or allowed change, aspect ratio/size and count. Do not automatically take the Cartesian product of every SKU, scene and ratio. Resolve mismatched SKU references rather than copying one product's label onto another.

Keep product color, label/logo/text, silhouette, proportions, materials and distinctive parts as explicit preservation targets. Product/SKU labels are task bookkeeping, not invented schema properties. If the user explicitly requests a color variant, describe it as a generated concept unless they provide a real reference confirming that product variant. Do not present a synthetic recoloring as evidence that the SKU exists.

Changing aspect ratio with a generative model can redraw the product and scene. It is not a lossless resize, crop or pixel-identical catalog conversion. Explain this distinction when exact pixels, labels, calibrated colors, measured geometry or print specifications matter. Do not promise alpha transparency or an unchanged product across sizes. If exact processing is essential, say the exposed tools do not provide that guarantee rather than silently substituting a generative edit.

## Source files and schema

For reference media, use externally fetchable HTTPS URLs that an unauthenticated GET can retrieve. When the host supplies such a URL for the user’s attachment and access is authorized for this task, use it directly; do not request another upload. Local paths, `file://`, internal attachment/sandbox IDs and data URIs cannot be passed to the Model API. Without a usable URL, explain the limit and request a direct link or a genuinely available, authorized host upload. These MCP tools do not upload arbitrary media: do not invent hosting, publish private media without permission, embed account credentials in URLs or repurpose training uploads.

Before a paid call, confirm each reference is a supported still image from reliable supplied metadata or an available inspection feature. A known HTML/login/model page, video or audio URL is not an image input merely because it is HTTPS or returns 200. If the media type is inaccessible or ambiguous, resolve it or request a direct supported image URL before a paid generation; do not claim a check you could not perform or invent an upload/conversion.

1. Select a currently exposed image operation that supports the actual source/reference images and requested edit or composition. Use `generate_image` when the current host exposes a 

Preview of the first 4,000 characters. Read full instructions →

stage-product-scenes8.45 KB

View saved version →

---
name: stage-product-scenes
description: Create requested product lifestyle or studio scenes from real product references with RunComfy. Use for reference-led product placement and scene concepts; does not guarantee unchanged SKU details, labels or physical geometry.
---

# Stage product scenes

Generate the requested scene around a supplied product, using this plugin's MCP tools. Respond in the user's language. No CLI, third-party skill or automatic media uploader is assumed.

Use only this plugin’s current host-provided tool definitions: actual names, descriptions, typed outer arguments and allowed model scope. If current definitions cannot be verified, report an unverified connection binding, not that RunComfy lacks the product capability. If verified definitions offer no compatible operation, explain the connection-specific limitation before spending. Do not assume a discovery tool, switch endpoints, invent operations or bypass the connection through workflow/deployment execution.

## Product and scene inputs

Keep a product checklist separate from the scene brief: product features to retain, surface/setting, placement, lighting and framing. Use a requested sales channel or placement only to inform supported composition and dimensions; do not claim marketplace approval. Return the requested scene with observed product/detail drift and unresolved checks.

Identify the actual product reference, intended SKU/variant/color, visible material, label/logo, shape and important parts. Ask the user to resolve conflicting references instead of blending different SKUs. If a second image is a scene/style reference, state that role and preserve reference order; do not treat every image as the same object.

Use the requested setting, surface, lighting, framing and count. A named product with no photo is insufficient to promise an accurate depiction: request an appropriate reference or offer a clearly described generic concept if the user accepts it. Never silently substitute stock-looking packaging for their real item.

Describe product preservation as an aim. Generative placement can change silhouette, dimensions, label text and color, and can invent unseen surfaces. Do not promise a measured scale rendering, exact logo reproduction, guaranteed catalog accuracy, or a true 3D/360-degree reconstruction from one image. Resolve exact-preservation requirements before spending.

## References and model choice

For reference media, use externally fetchable HTTPS URLs that an unauthenticated GET can retrieve. When the host supplies such a URL for the user’s attachment and access is authorized for this task, use it directly; do not request another upload. Local paths, `file://`, internal attachment/sandbox IDs and data URIs cannot be passed to the Model API. Without a usable URL, explain the limit and request a direct link or a genuinely available, authorized host upload. These MCP tools do not upload arbitrary media: do not invent hosting, publish private media without permission, embed account credentials in URLs or repurpose training uploads.

Before a paid call, confirm each reference is a supported still image from reliable supplied metadata or an available inspection feature. A known HTML/login/model page, video or audio URL is not an image input merely because it is HTTPS or returns 200. If the media type is inaccessible or ambiguous, resolve it or request a direct supported image URL before a paid generation; do not claim a check you could not perform or invent an upload/conversion.

1. Select a currently exposed image operation that supports the actual source/reference images and requested edit or composition. Use `generate_image` when the current host exposes a compatible definition, following its actual declared arguments and allowed model scope. A text-only operation cannot substitute for a required reference input.
2. Inspect the matched operation and supported model schemas for image fields, reference count/order, dimensions, ou

Preview of the first 4,000 characters. Read full instructions →

Release notes

Adds three product-photography skills for studio cleanup, lifestyle scenes and bounded campaign variants, with multilingual discovery terms, reference-input requirements, cost confirmation and request-bound result recovery. Aligns review cases with the current RunComfy Model API tools.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
RunComfy
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Create clean product photos
  • Stage product lifestyle scenes
  • Create product image variants
  • Check generation status

Package observed Nov 18, 2026.

Technical details
First seen
Nov 18, 2026 · 06:00 UTC
Last seen
Nov 18, 2026 · 06:00 UTC
Collection status
Collected

plugin_asdk_app_6aec2b743ad08191841f166091f52510

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.