Skip to main content
Glama

Place Product in Scene

sirv_place_product_in_scene

Place a product from an image into a new lifestyle scene described in text or styled by a reference image, creating 1–4 variations for marketing and listing photos.

Instructions

Place the product from one image into a new lifestyle scene. Describe the scene in scene_description, or give a style image in ref_image_url. Makes 1 to 4 variations.

Use it for marketing and listing photos. For a simple backdrop, use sirv_replace_background. To show clothing on a person, use sirv_try_on_garment.

The default model keeps the product's own pixels. The source image does not change. Returns the result URLs.

Credits: spends workspace credits. The cost depends on the model and options.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_url": "<image_url>"
    },
    "name": "sirv_place_product_in_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel. ideogram-keep keeps the product's own pixels; the others can redraw the product. Default: ideogram-keepideogram-keep
positionNoWhere the product sits, for manual_placement
image_urlYesPublic URL of the product image. A transparent background works best
num_resultsNoHow many variations to make, 1 to 4. Default: 1
ref_image_urlNoPublic URL of an image whose style the scene copies. Give this or scene_description
placement_typeNoHow the product is placed. original keeps its place in the photo; manual_placement uses position. Default: automaticautomatic
scene_descriptionNoThe scene, in words. Give this or ref_image_url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and non-idempotency, so the bar is lower; the description still adds real value by disclosing that the default model preserves the product's own pixels, that the source image is not modified, that result URLs are returned, and that workspace credits are spent with model-dependent cost. It does not quantify cost or latency, which keeps 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short paragraphs, front-loaded with the action, then alternatives, then behavior, then cost. Every sentence carries distinct information with no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter generative tool with no output schema, the description covers the return value (result URLs), the source-image safety guarantee, and the credit cost. Minor gaps remain around failure modes and how long generation takes, but nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter including the three enums is already documented. The description only restates the scene_description/ref_image_url either-or and the 1-to-4 variation count, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Place the product from one image into a new lifestyle scene') and immediately distinguishes itself from two named siblings, sirv_replace_background and sirv_try_on_garment, with the conditions that select each.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use ('marketing and listing photos') plus two when-not-to-use routes with named alternatives, so an agent can route correctly without opening other schemas.

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