Skip to main content
Glama

photoshop_export_artboards

Export every artboard in the active Photoshop document to a folder as separate PNG, JPEG, WebP, or AVIF files, one per artboard, without modifying the original.

Instructions

Export every artboard in the active document to a folder (duplicate + crop to artboardRect, then PNG/JPEG/WebP/AVIF).

Users often say: export all artboards, multi-screen PNG, 画板 çıktısı.

Use when: delivering one file per artboard. Long jobs use a 600s script timeout. Do NOT use when: exporting the whole canvas once — use photoshop_export_as.

Returns: JSON { ok, summary, details: { exported[], failed[], folder } }. Preconditions: document with at least one artboard. Side effects: writes files; does not modify the original.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "folder": "<folder>"
    },
    "name": "photoshop_export_artboards"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesAbsolute output folder (created if missing)
formatNoExport formatPNG
qualityNoQuality 0-100 (JPEG/WebP/AVIF)
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 observedv1.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states side effects ('writes files; does not modify the original'), preconditions ('document with at least one artboard'), the 600s script timeout for long jobs, and the return shape. This is comprehensive for a non-destructive export operation.

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?

The description is well-structured with labeled sections ('Use when', 'Do NOT use when', 'Returns', 'Preconditions', 'Side effects') and is front-loaded with the core purpose. It is slightly longer than necessary due to the multilingual user-phrase examples, but those aid intent recognition without bloating it.

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?

Given there is no output schema, the description correctly explains the return JSON. It covers the core operation, the sibling alternative, preconditions, side effects, timeout behavior, and parameter-relevant output details, so an agent has what it needs to invoke the tool 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 description coverage is 100%, so per the baseline the schema already documents all four parameters. The description adds slight context by listing the supported formats and mentioning the output folder, but it does not substantially expand on the schema's own parameter descriptions.

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: 'Export every artboard in the active document to a folder,' and includes the mechanism (duplicate + crop to artboardRect, then PNG/JPEG/WebP/AVIF). It also distinguishes itself from the sibling photoshop_export_as by explicitly saying that tool is for exporting the whole canvas once.

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?

The description gives explicit when-to-use guidance: 'delivering one file per artboard.' It also provides a clear exclusion and alternative: 'Do NOT use when: exporting the whole canvas once — use photoshop_export_as.' This leaves little ambiguity for an agent selecting among siblings.

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