Skip to main content
Glama

Place Product in a Scene

place_product

Put the user's own product photo into a real-looking scene, keeping the product as it is (no people, faces or added text). Paid plans only. The photo must already be uploaded to HalalGen: pass its link as product_image_url, or call without it to list the user's uploads. Scenes: marble counter, desert dunes, boutique shelf, kitchen table, Ramadan lantern table, colour backdrop, or one they describe. 1–4 pictures, charged per picture (see list_models or estimate_cost).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "place_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoHow big the product is in the frame.medium
countNoHow many pictures (each one is charged).
lightNomorning = soft bright light, golden = warm sunset light, night = dark with warm lamps.morning
sceneNomarble = white marble kitchen counter, dunes = desert sand dunes, shelf = boutique shop shelf, kitchen = rustic kitchen table, lantern = Ramadan table with brass lanterns and dates, studio = plain colour backdrop, custom = describe it in custom_scene.studio
positionNoWhere the product sits in the picture.center
aspect_ratioNoPicture shape: 1:1 square, 4:5 feed post, 9:16 story, 16:9 banner.1:1
custom_sceneNoOnly for scene 'custom': where the product stands, e.g. 'on a stone step beside a small fountain in a tiled courtyard'. No people.
backdrop_colorNoOnly for scene 'studio': the backdrop colour.sand
product_image_urlNoLink to a product photo the user uploaded to HalalGen (https://api.halalgen.ai/image/uploads/... or https://cdn.halalgen.ai/uploads/...). Other links are refused. Leave empty to list the user's uploads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare non-readonly, openWorld and non-idempotent, and the description adds genuinely new behavior: paid-plan gating, upload-domain validation, per-picture billing for 1–4 images, the fact that a no-URL call returns an upload listing instead of generating, and hard content restrictions. That is exactly the extra context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Single dense paragraph, front-loaded with the core action and immediately followed by the hard prerequisites and cost note. Efficient overall, though the scene enumeration and billing aside are packed into the same run-on sentence rather than separated.

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?

Nine optional params, no output schema, and the description covers prerequisites, billing, URL validation and the fallback listing behavior. The main remaining gap is that it never says what a successful call returns (image URL? generation ID? is polling needed?), which matters for a paid, non-idempotent generation tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still earns above that by spelling out the scene palette in plain language and clarifying that count drives per-picture charges. It does not add guidance on size, position, or aspect_ratio beyond the enum docs, so it does not fully cover the parameter space.

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

Purpose4/5

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

Specific verb + resource: 'Put the user's own product photo into a real-looking scene, keeping the product as it is.' A constraint clause ('no people, faces or added text') further narrows the outcome, implicitly separating it from generate_image and edit_image. It stops short of naming a sibling explicitly, so sibling differentiation relies on inference.

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

Usage Guidelines4/5

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

Strong prerequisites ('Paid plans only', photo must already be uploaded to HalalGen, other links refused) and an explicit conditional behavior: call without product_image_url to list the user's uploads. It also routes to estimate_cost / list_models for pricing. What it lacks is an explicit when-to-use-this-instead-of-generate_image rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources