Skip to main content
Glama
alisaitteke

Photoshop MCP Server

by alisaitteke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_create_artboard

Create a Photoshop artboard at a set origin or to the right of existing artboards to build multi-screen layouts and iPhone frames.

Instructions

Create a Photoshop artboard (AM artboardSection) at an explicit origin or placed to the right of existing artboards.

Users often say: add iPhone frame, new artboard, multi-screen layout, 画板 ekle.

Use when: building a multi-device / multi-screen document. First artboard converts a regular canvas into an artboard document. Do NOT use when: you only need a new document tab — use photoshop_create_document.

Returns: JSON { ok, summary, details: { artboard, count } }. Preconditions: active document. Side effects: adds an artboard layer group.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoTop origin in pixels (default: aligned with existing artboards, or 0)
leftNoLeft origin in pixels (default: 32px to the right of existing artboards, or 0)
nameNoArtboard name (default Artboard)
widthYesArtboard width in pixels
heightYesArtboard height in pixels
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: -[
-  "width",
-  "height"
-]New value: +[
+  "width",
+  "height",
+  "document_id"
+]
  3. Addedv1.7.20

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover the mutation profile (readOnly=false, destructive=false, idempotent=false), and the description adds genuinely new behavioral facts: preconditions ('active document'), side effects ('adds an artboard layer group'), and a non-obvious state transition ('First artboard converts a regular canvas into an artboard document').

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 verb+resource, then labeled sections (Use when / Do NOT use when / Returns / Preconditions / Side effects). Every line carries distinct information; no filler sentences.

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?

Although there is no output schema, the description specifies the return shape ({ ok, summary, details: { artboard, count } }), preconditions, and side effects. For a 6-parameter mutation tool, an agent has everything needed to call it correctly.

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 coverage is 100%, so parameters are already fully documented in the schema. The description adds only the high-level notion of 'explicit origin or placed to the right of existing artboards', which largely restates the schema's left/top defaults. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Create a Photoshop artboard (AM artboardSection)') and immediately distinguishes it from the neighboring sibling by giving the alternative explicitly (photoshop_create_document). The scope is clear enough that an agent can select it without opening the schema.

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?

Contains explicit 'Use when' (multi-device/multi-screen documents, first artboard converting a canvas) and 'Do NOT use when' (need a new document tab → photoshop_create_document) sections. Also supplies trigger phrases users actually say, which is directly actionable for routing.

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