Skip to main content
Glama

Place person in scene

place_person_in_scene

Use only with the user's own likeness or content they are authorized to use. Do not use for impersonation, deception, sexual content, or content involving minors.

Places a person from one supplied photo into a supplied scene image. Cost depends on resolution (from 50 credits at 640px); returns a project id for wait_for_image_project. Before choosing settings, read get_account_info and the current parameter constraints. A listed model, resolution, duration or count is not necessarily available together or on this account. Preserve explicit requirements and all supplied inputs; explain a genuine block instead of submitting an incompatible request. Account balance alone does not prove a request is affordable. Use the named attachment fields first for ChatGPT files. Ask which file goes where if their roles are unclear. If a file fails, ask the user to attach it again and keep the requested settings.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional project name for identifying this output. Omit to use the API's default project name.Body Swap - dateTime
assetsNoPerson image and scene image for body swap
resolutionYesOutput resolution. Determines credits charged for the run.
scene_imageNoAttach the scene image from ChatGPT for this input.
person_imageNoAttach the person image from ChatGPT for this input.

Output Schema

NameRequiredDescriptionDefault
idYesUnique ID of the image. Use it with the [Get image Project API](https://docs.magichour.ai/api-reference/image-projects/get-image-details) to fetch status and downloads.
credits_chargedYesThe amount of credits deducted from your account to generate the image. We charge credits right when the request is made. If an error occurred while generating the image(s), credits will be refunded and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / allOf
      Added value: +[
      +  {
      +    "anyOf": [
      +      {
      +        "required": [
      +          "person_image"
      +        ]
      +      },
      +      {
      +        "properties": {
      +          "assets": {
      +            "required": [
      +              "person_file_path"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "assets"
      +        ]
      +      }
      +    ]
      +  },
      +  {
      +    "anyOf": [
      +      {
      +        "required": [
      +          "scene_image"
      +        ]
      +      },
      +      {
      +        "properties": {
      +          "assets": {
      +            "required": [
      +              "scene_file_path"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "assets"
      +        ]
      +      }
      +    ]
      +  }
      +]
    • removedInput schema / properties / assets / required
      Removed value: -[
      -  "person_file_path",
      -  "scene_file_path"
      -]
    • addedInput schema / properties / person_image
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Attach the person image from ChatGPT for this input.",
      +  "properties": {
      +    "download_url": {
      +      "description": "Exact HTTPS download URL supplied for the native ChatGPT attachment, including its signed query.",
      +      "title": "Download Url",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "description": "Native ChatGPT file identifier paired with download_url; not a local filesystem path.",
      +      "title": "File Id",
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "default": "",
      +      "description": "Original attachment filename, when supplied by ChatGPT.",
      +      "title": "File Name",
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "default": "",
      +      "description": "Attachment MIME type, when supplied by ChatGPT.",
      +      "title": "Mime Type",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "title": "ChatGPTFile",
      +  "type": "object"
      +}
    • addedInput schema / properties / scene_image
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Attach the scene image from ChatGPT for this input.",
      +  "properties": {
      +    "download_url": {
      +      "description": "Exact HTTPS download URL supplied for the native ChatGPT attachment, including its signed query.",
      +      "title": "Download Url",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "description": "Native ChatGPT file identifier paired with download_url; not a local filesystem path.",
      +      "title": "File Id",
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "default": "",
      +      "description": "Original attachment filename, when supplied by ChatGPT.",
      +      "title": "File Name",
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "default": "",
      +      "description": "Attachment MIME type, when supplied by ChatGPT.",
      +      "title": "Mime Type",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "title": "ChatGPTFile",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "resolution",
      -  "assets"
      -]New value: +[
      +  "resolution"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Give your image a custom name for easy identification."New value: +"Optional project name for identifying this output. Omit to use the API's default project name."
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

Big addition on the cost model for a non-destructive but billed mutation. It also warns that listed options may not be available together or on this account, so account balance alone doesn't prove affordability. That said, several sentences are generic agent-policy boilerplate ("Preserve explicit requirements", "explain a genuine block") that reads more like instructions than disclosure of what the tool does.

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

Conciseness3/5

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

Not front-loaded: the leading sentences are a safety policy rather than what the tool does, so the actual operation appears second. Policy and process sentences are defensible, but generic compliance phrasing adds length without new information.

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?

Complete for a complex tool with nested anyOf attachment alternatives. It routes the caller to wait_for_image_project for the returned project id, which the output schema alone wouldn't imply. Remaining gaps are minor given the fully documented schema.

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 baseline 3, and the description still improves the choice of the resolution enum by stating a concrete price floor (50 credits at 640px) and that the listed options aren't guaranteed to be combinable. It does not explain any nuance of the person/scene attachment versus file-path alternative, which the schema already handles.

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?

States a concrete verb and resource: "Places a person from one supplied photo into a supplied scene image." That is unambiguous and distinguishable from single-purpose siblings like swap_face_in_photo or change_clothes_in_photo, though it never names an alternative to route against.

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

Usage Guidelines4/5

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

Gives explicit prerequisites and workflow routing: read get_account_info and the current parameter constraints before choosing settings, prefer the named attachment fields for ChatGPT files, ask which file goes where if roles are unclear, and re-request a failed attachment while keeping settings. It also states hard policy exclusions (impersonation, deception, sexual content, minors). What's missing is when to pick this over a sibling face/character tool.

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.