Skip to main content
Glama

Edit face in photo

edit_face_in_photo

Adjusts facial expression, pose and gaze in a supplied photo using numeric controls. Costs 1 credit per edit; output size depends on the subscription tier. Starts a background job; 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.Face Editor - dateTime
imageNoAttach the image from ChatGPT for this input.
styleYesFace editing parameters
assetsNoProvide the assets for face editor

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. Changed4 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "image"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "assets": {
      +        "required": [
      +          "image_file_path"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "assets"
      +    ]
      +  }
      +]
    • removedInput schema / properties / assets / required
      Removed value: -[
      -  "image_file_path"
      -]
    • addedInput schema / properties / image
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Attach the 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: -[
      -  "assets",
      -  "style"
      -]New value: +[
      +  "style"
      +]
  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?

Annotations already flag this as a non-read-only, non-idempotent, open-world mutation, and the description adds real value on top: 1 credit per edit, output size tied to subscription tier, and background-job semantics returning a project id. However, several sentences are generic account/file-hygiene policy that could be pasted into any tool in this family, so the behavioral payload is diluted.

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?

Purpose, cost and async behavior are correctly front-loaded, but the tail of the description contains several generic admonitions ('Preserve explicit requirements and all supplied inputs', 'Account balance alone does not prove a request is affordable') that are policy boilerplate rather than tool-specific instruction. Roughly a third of the text does not earn its place for this particular tool.

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?

With an output schema present, the description does not need to explain return values, and it still helpfully states that a project id is returned for polling. Combined with credit cost and the account-info prerequisite, it is close to complete for a nested-schema, async mutation tool; the remaining gap is guidance on when a different face tool is the right choice.

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 description coverage is 100%, so the baseline is 3, but the description adds a precedence rule the schema does not encode: 'Use the named attachment fields first for ChatGPT files' and 'Ask which file goes where if their roles are unclear,' which clarifies the image vs assets anyOf. It still says nothing about the meaning or directionality of the numeric style controls, which the schema handles alone.

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?

The description opens with a specific verb and resource — 'Adjusts facial expression, pose and gaze in a supplied photo using numeric controls' — which tells an agent exactly what the tool produces. It does not, however, contrast itself with the nearby sibling swap_face_in_photo or swap_head_in_photo, so the agent must infer which face-manipulation tool applies.

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?

It gives concrete prerequisites — read get_account_info and current parameter constraints before choosing settings — and routes the agent to wait_for_image_project for the asynchronous result. What is missing is any when-not guidance, e.g. when to prefer swap_face_in_photo instead of editing expression/pose on an existing face.

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.