Free Photoshop MCP

Abrir archivo

ps_open

Opens PSD, PSB, image, PDF, or AI files in Photoshop and returns the document's configuration, giving AI agents the file details needed to continue.

Instructions

Abre un PSD/PSB/imagen/PDF/AI en Photoshop y devuelve su configuración.

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": {
      "path": "<path>"
    },
    "name": "ps_open"
  }
}

Input Schema

Name	Required	Description
`page`	No	Página (PDF/AI)
`path`	Yes	Ruta absoluta
`resolution`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It says the file is opened and configuration returned, but does not disclose whether it replaces/opens a new document, permission or session requirements, supported failure modes, or what 'configuración' contains.

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?

A single, front-loaded sentence with no wasted words. Efficient, though its brevity is partly under-specification rather than pure conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and 'devuelve su configuración' only vaguely gestures at the return value. For an open/file-loading tool with no annotations and one undocumented parameter, the definition is minimally adequate but leaves open questions.

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 67%: path and page are self-documented in the schema, while resolution has no description in either place. The description only echoes the accepted file formats, adding little param-level detail, so a baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Abre') and the resource set (PSD/PSB/imagen/PDF/AI) and notes it returns configuration. Clear enough to distinguish from ps_new_document, but it does not explicitly differentiate from other file-producing siblings like ps_close or ps_save.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to use this tool versus alternatives such as ps_new_document or ps_place_image, no prerequisites (e.g., needs an active Photoshop session), and no exclusions are given. The agent must infer context entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.