Skip to main content
Glama

photoshop_export_as

Export the active Photoshop document or one selected artboard as PNG, JPEG, WebP, or AVIF without changing the open file.

Instructions

Export a copy of the active document as PNG, JPEG, WebP or AVIF without changing the open document. WebP/AVIF require Photoshop 23.2+/recent builds and return a clear error when unsupported.

Users often say: export for web, save as webp, quick export png.

Use when: web-ready delivery formats are needed (WebP/AVIF/modern pipelines), or one artboard from a multi-screen file. Do NOT use when: saving the working document itself — use photoshop_save_document. For every artboard at once use photoshop_export_artboards.

Returns: JSON { ok, summary, details: { path, format, method, artboard_id? } }. Preconditions: active document. Side effects: writes one file to path. Optional artboard_id exports only that board (duplicate + crop).

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute output file path (extension should match format)
formatNoExport formatPNG
qualityNoQuality 0-100 (JPEG/WebP/AVIF)
artboard_idNoOptional artboard layer id from photoshop_list_artboards — export that board only instead of the full canvas
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.9/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses side effects ('writes one file to path'), non-destructive behavior ('without changing the open document'), preconditions ('active document'), version requirements for WebP/AVIF, and the duplicate+crop behavior for artboard_id. This is exceptional transparency for an unannotated tool.

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?

The description is organized with labeled sections (use when, do not use, returns, preconditions, side effects) and every sentence adds operational value. It is longer than average, but the length is justified by the tool's branching behaviors and the absence of annotations.

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 no output schema and no annotations, the description fully covers the return shape, side effects, preconditions, format constraints, and artboard-specific behavior. The input schema handles parameter details, and the description supplies the operational context an agent needs to call this tool safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 each parameter. The description adds meaningful context beyond the schema, such as the version requirement tied to format, the 'duplicate + crop' semantics of artboard_id, and the path/extension matching expectation, which helps an agent invoke parameters correctly.

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 ('Export a copy'), the resource ('active document'), and the supported formats. It explicitly says the open document is unchanged, which distinguishes it from save operations, and names sibling alternatives like photoshop_save_document and photoshop_export_artboards.

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' and 'Do NOT use when' guidance, naming photoshop_save_document for saving the working document and photoshop_export_artboards for exporting every artboard. It also includes natural-language user phrasings like 'export for web' and 'save as webp' that help an agent recognize intent.

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