Skip to main content
Glama
alisaitteke

Photoshop MCP Server

by alisaitteke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_recipe_split_carousel

Split an active wide Photoshop document into N equal vertical slices and export sequentially numbered files for a swipeable Instagram/TikTok carousel.

Instructions

Split the active wide document into N equal vertical slices and export them as sequentially numbered files for a seamless Instagram/TikTok carousel (panorama swipe effect).

Use when: the user wants a seamless/swipeable carousel, split panorama, or multi-slide export of one wide design. Typical request: "split this into a 5-slide carousel". Do NOT use when: the user wants the same content reframed per platform (use photoshop_recipe_export_social_variants) or a single crop (use photoshop_crop_document).

Returns: { ok, summary, output_paths (in slide order), details: { slides, slice_width } }.

Preconditions: active document whose width is at least slides pixels. Side effects: writes one file per slide; source document is unchanged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoOutput format. Default jpg.jpg
slidesYesNumber of carousel slides to split into (2-10).
qualityNoJPEG quality on the Photoshop 1-12 scale (jpg only). Default 10.
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.
slide_widthNoOptional final slide width in px (e.g. 1080). Requires slide_height. Each slice is center-cropped/resized to this size. Omit to keep native slice dimensions.
slide_heightNoOptional final slide height in px (e.g. 1350 for Instagram portrait). Requires slide_width.

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: -[
-  "slides"
-]New value: +[
+  "slides",
+  "document_id"
+]
  3. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare the write/idempotency profile, but the description goes further by disclosing a precondition (active document width must be at least `slides` pixels) and side effects (one file written per slide, source document left unchanged). Those are behavioral facts the annotations do not convey and that matter for a non-idempotent, non-readonly export.

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-loads the core action in the first sentence, then uses labelled sections (Use when / Do NOT use when / Returns / Preconditions / Side effects) that are scannable and waste-free. Every sentence carries information an agent needs to call the tool correctly.

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?

For a 6-parameter export tool with no output schema, the description compensates fully: it specifies preconditions, side effects, the return shape ({ ok, summary, output_paths, details }) and the sibling alternatives. Nothing an agent needs in order to invoke it 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%, so the schema already documents every parameter including enum, ranges and defaults, giving a baseline of 3. The description only reinforces the slice concept and the slide-order return; it adds no format, constraint or interdependency detail beyond what the schema states.

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 (Split) and resource (active wide document) with the exact output behavior (N equal vertical slices exported as sequentially numbered files) and the use case (Instagram/TikTok carousel). It explicitly differentiates itself from photoshop_recipe_export_social_variants and photoshop_crop_document, so an agent can route correctly without opening any 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' and 'Do NOT use when' blocks, names the two alternative tools for the excluded cases (reframed per-platform content, single crop), and gives a concrete triggering request example. This is exactly the when/when-not/alternatives structure that maximises routing accuracy.

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