Skip to main content
Glama
alisaitteke

Photoshop MCP Server

by alisaitteke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_create_document

Create a new empty Photoshop document with set width, height, resolution, and color mode to start a design from scratch when no canvas is open.

Instructions

Create a new empty Photoshop document with specified dimensions and color mode.

Use when: starting a design from scratch or no document is open. Do NOT use when: opening an existing file — use photoshop_open_image.

Returns: created document id and name. Preconditions: none. Side effects: creates a new document and makes it active.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
widthNoDocument width in pixels. Default 1920 when the request names no size.
heightNoDocument height in pixels. Default 1080 when the request names no size.
colorModeNoColor mode (RGB, CMYK, Grayscale)RGB
resolutionNoDocument resolution in DPI (default: 72)
document_idNoIgnored. photoshop_create_document and photoshop_open_image do not target an existing tab. Omit this, or send null or 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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: +"Ignored. photoshop_create_document and photoshop_open_image do not target an existing tab. Omit this, or send null or 0."
    • changedInput schema / required
      Previous value: -[
-  "document_id"
-]New value: +[]
  2. Changed8 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"
+]
    • addedInput schema / properties / height / default
      Added value: +1080
    • changedInput schema / properties / height / description
      Previous value: -"Document height in pixels"New value: +"Document height in pixels. Default 1080 when the request names no size."
    • addedInput schema / properties / width / default
      Added value: +1920
    • changedInput schema / properties / width / description
      Previous value: -"Document width in pixels"New value: +"Document width in pixels. Default 1920 when the request names no size."
    • changedInput schema / required
      Previous value: -[
-  "width",
-  "height"
-]New value: +[
+  "document_id"
+]
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is partly covered; the description adds genuinely new context by stating there are no preconditions and that the tool makes the new document active. It does not address edge behavior such as what happens if a document is already open, so it falls short of a 5.

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?

Four labeled, front-loaded lines covering purpose, routing, returns, and side effects with zero filler. The alternative tool is called out early enough to redirect an agent before it reads further.

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 compensates by naming the return values (document id and name), and it closes the two remaining gaps an agent would care about — preconditions and side effects. Nothing needed to invoke this tool correctly is missing.

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 every parameter (including defaults and the intentionally-ignored document_id) is documented in the schema itself. The description only echoes 'dimensions and color mode' without adding format or unit detail, so the baseline 3 applies.

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 and resource ('Create a new empty Photoshop document') plus the configurable axes (dimensions, color mode). It explicitly differentiates itself from the nearest sibling by naming photoshop_open_image as the tool to use for existing files.

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?

Provides explicit 'Use when' (starting from scratch, no document open) and 'Do NOT use when' (opening an existing file) clauses, and routes to the correct alternative by name. Nothing about tool selection is left to inference.

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