IDPhoto.ai Passport & Visa Photos

Make ID photo

make_id_photo

Turn a portrait photo into a compliant passport / visa / ID photo for a given document spec (cropping, resizing, background replacement, quality checks). Returns a temporary download URL for the finished JPEG, its pixel/physical size, and any detected quality issues (e.g. ISSUE_EYEGLASSES_NOT_ALLOWED) that may require a retake. Use list_photo_specs or get_photo_spec first if you are unsure of the specCode. The input image must be base64 (data URI prefix allowed), at most ~4 MB decoded, showing one person facing the camera. Without API credentials this is limited to 3 photos per day.

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": {
      "specCode": "<specCode>",
      "imageBase64": "<imageBase64>"
    },
    "name": "make_id_photo"
  }
}

Input Schema

Name	Required	Description	Default
`specCode`	Yes	Document spec code, e.g. 'us-passport', 'uk-passport', 'schengen-visa'. Specs starting with 'ai-' use AI generation and may be slow.
`imageBase64`	Yes	Source portrait as base64 (JPEG/PNG). A 'data:image/jpeg;base64,' prefix is optional.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

removedInput schema / properties / autoFixShoulder

Removed value: -{
-  "description": "Try to automatically fix uneven/cut-off shoulders. Default false.",
-  "type": "boolean"
-}

removedInput schema / properties / photoSheetSizes

Removed value: -{
-  "description": "Optional printable sheet sizes in pixels as 'WIDTH*HEIGHT' (e.g. '1800*1200' = 6x4 in at 300 DPI). Returns a sheet URL per size.",
-  "items": {
-    "pattern": "^\\d{2,5}\\*\\d{2,5}$",
-    "type": "string"
-  },
-  "maxItems": 10,
-  "type": "array"
-}

First observedOct 19, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), and the description adds context those annotations cannot convey: a temporary download URL return, quality-issue codes like ISSUE_EYEGLASSES_NOT_ALLOWED that may force a retake, an ~4 MB decoded size ceiling, and a 3-photos-per-day quota without credentials. These are exactly the operational constraints an agent needs before invoking.

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?

Front-loaded with the core transformation, then the return shape, then the specCode prerequisite, then input constraints and the quota. Every sentence carries a distinct fact (what it does, what it returns, what to call first, input limits) with no filler.

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

Completeness5/5

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

With no output schema, the description must describe returns, and it does: a temporary download URL, pixel/physical size, and detected quality issues. Combined with input limits, prerequisites, and quota, an agent has everything needed to call this correctly and interpret the response.

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, but the description adds real meaning beyond the schema: it tells the agent to resolve specCode via the sibling lookup tools and that the image must be base64 with an optional data URI prefix, at most ~4 MB decoded, depicting one person facing the camera. The size and content constraints are not in the 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?

States a specific verb+resource+outcome: converting a portrait into a compliant passport/visa/ID photo for a given document spec, enumerating the operations (cropping, resizing, background replacement, quality checks). It is clearly distinguishable from siblings get_photo_spec and list_photo_specs, which only resolve spec codes.

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?

Explicitly routes the agent: 'Use list_photo_specs or get_photo_spec first if you are unsure of the specCode', naming both alternatives and the condition that selects them. It also states input preconditions (one person, facing camera, base64 format) and a usage limit without credentials, so the agent knows when this call is viable.

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

All IDPhoto.ai Passport & Visa Photos tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?