Skip to main content
Glama
alisaitteke

Photoshop MCP Server

by alisaitteke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_generate_image

Generate a new image in Photoshop from a text prompt to create visual assets from descriptions without manual drawing.

Instructions

Photoshop Generate Image (Firefly ImageGen): create an image from a text prompt.

Use when: the user asks for ImageGen, text-to-image, or a new picture from a description.

Returns: { ok, summary, details }. Preconditions: generative_fill capability; Adobe generative credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNoWidth if creating new doc (default 1024)
heightNoHeight if creating new doc (default 1024)
promptYesImage description
document_idYesPhotoshop document id from photoshop_get_state / photoshop_list_documents. Send null or 0 to use the active document. A positive number activates that document before the tool runs. When no document is open, a stale id does not block the call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.33
    • changedInput schema / properties / document_id / description
      Previous value: -"Photoshop document id from photoshop_get_state / photoshop_list_documents. Send null to use the active document. A number activates that document before the tool runs."New value: +"Photoshop document id from photoshop_get_state / photoshop_list_documents. Send null or 0 to use the active document. A positive number activates that document before the tool runs. When no document is open, a stale id does not block the call."
  2. Changed4 schema fields changedv1.7.32
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / document_id / description
      Previous value: -"Optional 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."New value: +"Photoshop document id from photoshop_get_state / photoshop_list_documents. Send null to use the active document. A number activates that document before the tool runs."
    • changedInput schema / properties / document_id / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedInput schema / required
      Previous value: -[
-  "prompt"
-]New value: +[
+  "prompt",
+  "document_id"
+]
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the mutating, non-idempotent, open-world, non-destructive profile, and the description adds value beyond that: a preconditions block naming the generative_fill capability and Adobe generative credit consumption, plus an explicit return shape. It doesn't clarify whether the result lands in a new document or a new layer, which is the main behavioral unknown.

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?

Four short labeled lines (purpose, Use when, Returns, Preconditions) with the purpose front-loaded and zero filler. The labeled format is slightly mechanical but every line carries information an agent would otherwise have to infer.

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?

For a 4-parameter, no-output-schema tool the description covers purpose, triggers, return shape, and capability/credit prerequisites, so the calling agent has enough to invoke it. The remaining ambiguity is whether output goes to a new document (implied by width/height) or the active document, which the description never resolves.

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%, so prompt, document_id, width, and height are already documented in the schema, including the null/0 active-document convention and stale-id tolerance. The description adds no extra parameter meaning, so the baseline 3 applies.

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 specific verb and resource ('create an image from a text prompt') and adds the engine qualifier (Firefly ImageGen / text-to-image), which separates it from generic image tools. It does not explicitly contrast with the nearest siblings such as photoshop_generative_fill or photoshop_place_image, so an agent still has to reason about whether it wants generation or placement.

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?

The 'Use when' clause gives concrete trigger conditions (user asks for ImageGen, text-to-image, or a new picture from a description), which is clear routing guidance. It stops short of stating when NOT to use it (e.g., inpainting inside a selection should use photoshop_generative_fill instead), so the sibling boundary is left implicit.

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