Free Photoshop MCP

Capturar estilo de una capa

ps_capture_style

Capture a layer's effects, blend mode, fill, and text typography as a reusable style recipe. Save it by name to apply later via effects:{recipe}.

Instructions

Lee los efectos, mezcla, relleno y (si es texto) la tipografía de una capa como receta reutilizable. Con name la guarda en el estilo activo para usarla luego con effects:{recipe}.

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": {
      "layer": "<layer>"
    },
    "name": "ps_capture_style"
  }
}

Input Schema

Name	Required	Description
`doc`	No	Documento (nombre o índice desde 1). Por defecto el activo.
`name`	No	Guardarla como receta con este nombre
`layer`	Yes	Capa: nombre, 'Grupo/Capa', id numérico o {id\|name\|path\|index\|nth}

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 17, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the operation reads style attributes and optionally persists them under a name (a state-changing side effect), which is useful. However it does not cover permissions, what happens on name collision, or the return shape of the recipe, leaving clear gaps.

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?

Two tight sentences with the core action front-loaded, followed by the persistence behavior. No filler, though the effects:{recipe} reference assumes prior knowledge.

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

Completeness4/5

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

For a 3-parameter read/capture tool with a fully documented schema and no output schema, the description conveys the essential behavior (what is read, the recipe output, and optional saving). It stops short of clarifying sibling relationships and edge cases, so not a 5.

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 `doc`, `name`, and `layer`. The description mainly restates the `name` behavior already in the schema and adds no syntax or format detail beyond it, matching the baseline 3.

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 (lee/captura) and resource (efectos, mezcla, relleno, tipografía de una capa), and explains it produces a reusable recipe. It does not distinguish itself from the similar-sounding sibling ps_style_get or ps_style_analyze, so a 4 rather than a 5.

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

Usage Guidelines3/5

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

It implies usage by noting that passing `name` saves the recipe into the active style for later use via effects:{recipe}, which is helpful context. But it never says when to use this instead of ps_style_get, ps_style_list, or ps_style_analyze, so the guidance is only implicit.

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