Skip to main content
Glama
alisaitteke

Photoshop MCP Server

by alisaitteke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_recipe_passport_photo

Convert a portrait into a passport/ID photo: replace background with white, crop to ICAO headroom, resize to official pixels at 300 DPI, and export JPEG. Optionally build a 10x15cm print sheet.

Instructions

Turn the active portrait into a passport/ID photo: removes the background via Select Subject, replaces it with white, crops around the subject with ICAO-style headroom, resizes to the exact official pixel size at 300 DPI, and exports a JPEG. Optionally also builds a 10×15 cm print sheet with multiple copies.

Use when: passport photo, visa photo, ID photo, vesikalık, biyometrik fotoğraf. Do NOT use when: the document has no clear single subject, or official compliance must be guaranteed — head-size rules are approximated from subject bounds (no face detection); official acceptance is NOT guaranteed.

Returns: { ok, summary, output_paths, details: { spec, width, height, sheet } }.

Preconditions: PS ≥ 23 (Select Subject v2); active document with a single-person portrait. Side effects: writes one JPEG (+ one sheet JPEG when make_sheet); source document is unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specNoTarget size: us_2x2 (600×600 px), eu_35x45 (413×531 px), tr_50x60 (591×709 px). All at 300 DPI. Default us_2x2.us_2x2
qualityNoJPEG quality on the Photoshop 1-12 scale. Default 11.
make_sheetNoAlso export a 10×15 cm (1200×1800 px @300 DPI) print sheet tiled with copies. Default false.
document_idNoOptional Photoshop document id from photoshop_get_state / photoshop_list_documents. When set, the tool activates that document before running so a UI tab switch cannot retarget the edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses the full multi-step workflow, preconditions (PS ≥ 23, active single-person portrait), side effects (writes JPEG outputs, source unchanged), and limitations (head-size approximated, no face detection, official acceptance not guaranteed).

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?

The description is well-structured with a front-loaded summary, usage directions, return shape, preconditions, and side effects. Every sentence carries distinct useful information and the formatting makes it easy for an agent to scan.

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?

This is a complex multi-step recipe with no output schema, yet the description explains the return object shape, what files are written, preconditions, and failure-relevant limitations. An agent has enough context to decide, invoke, and interpret the result.

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

Parameters3/5

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

Schema description coverage is 100% and each parameter already has detailed descriptions including enum values, dimensions, defaults, and behavior (e.g. document_id activation semantics). The description adds modest framing like 'official pixel size at 300 DPI' and '10×15 cm print sheet', but does not materially go beyond 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?

The description opens with a specific verb and resource: 'Turn the active portrait into a passport/ID photo', followed by a concrete pipeline of operations (Select Subject, white background, crop, resize, export). This clearly separates it from generic sibling tools like photoshop_crop_document or photoshop_export_as and from other recipes.

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?

Explicit 'Use when' and 'Do NOT use when' sections give concrete triggers (passport/visa/ID photo) and exclusions (no clear subject, official compliance must be guaranteed). The only missing piece is a named alternative tool to use instead in the excluded cases.

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

Deploy Server

Other Tools