Skip to main content
Glama
photo-ai-studio

Photo AI Studio MCP Server

Official
by photo-ai-studio
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

edit_image

Apply 19 AI operations to edit photos, including background removal, skin retouching, age change, face swap, and more. Choose an operation and provide the required inputs.

Instructions

Edit a photo using one of 19 AI operations. Credit costs: remove_background (10), replace_background (3), all others (100).

Operations:

  • remove_background: Remove image background (image_url required)

  • replace_background: Replace background with prompt (image_url, prompt required)

  • retouch: AI retouch with prompt guidance (image_url, prompt required)

  • skin: Smooth and enhance skin (image_url required)

  • hair: Change hairstyle (image_url required, hairstyle or reference_image_url)

  • makeup: Apply AI makeup (image_url required)

  • age: Change apparent age (image_url, target_age required)

  • expression: Change facial expression (image_url, target_expression required)

  • body_type: Modify body type (image_url, target_body_type required)

  • eye_color: Change eye color (image_url, target_eye_color required)

  • color_correction: Auto color correction (image_url required)

  • custom: Custom AI edit with prompt (image_url, prompt required)

  • clothes: Change clothes (image_url, clothes_image_url required)

  • try_on: Virtual clothes try-on (image_url, clothes_image_url required)

  • product: Product placement (image_url, product_image_url required)

  • upscale: Enhance resolution (image_url required)

  • restore: Restore old/damaged photo (image_url required)

  • face_swap: Swap faces between photos (source_image_url, target_image_url required)

  • extend: Extend image canvas (image_url required)

All image URLs must be CDN URLs from upload_image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesThe edit operation to perform
image_urlNoCDN URL of the image to edit (required for all operations except face_swap)
promptNoText prompt for replace_background, retouch, custom operations
hairstyleNoTarget hairstyle for hair operation
hair_colorNoTarget hair color for hair operation
reference_image_urlNoReference image URL for hair or custom operations
target_ageNoTarget age for age operation
target_expressionNoTarget expression for expression operation (e.g. "happy", "serious")
target_body_typeNoTarget body type for body_type operation
target_eye_colorNoTarget eye color for eye_color operation
clothes_image_urlNoClothes image URL for clothes/try_on operations
product_image_urlNoProduct image URL for product operation
source_image_urlNoSource face image for face_swap operation
target_image_urlNoTarget image for face_swap operation
num_imagesNoNumber of variations for try_on operation
wait_for_resultNoIf true (default), waits for the result. If false, returns prediction_id immediately.

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

Discloses credit costs, required parameters per operation, and the 'wait_for_result' behavior. Missing details on idempotency, rate limits, or side effects, but adequate given no annotations.

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?

Well-structured with bullet points and clear sections. Could be slightly more concise, but every sentence adds necessary information.

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

Completeness3/5

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

No output schema; the description does not explain the return format (e.g., edited image URL or prediction ID) for most operations, leaving the agent uncertain about what to expect.

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%, but the description adds value by mapping operations to required parameters and providing examples, which helps the agent understand usage beyond raw schema.

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?

The description clearly states it edits photos using 19 AI operations, with a specific verb and resource. It distinguishes from siblings like 'generate_photo' and 'create_video' by focusing on editing existing images.

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?

Provides explicit guidance on which operation requires which parameters and credit costs. However, it does not explicitly state when to avoid this tool in favor of alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/photo-ai-studio/photo-ai-studio-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server