Skip to main content
Glama

Modificar capa

ps_set_layer

Set or modify Photoshop layer properties—name, visibility, position, opacity, blend mode, order, mask, and effects—to update a layer in one call.

Instructions

Cambia casi todo de una capa: nombre, visibilidad, opacidad, relleno, modo de fusión, recorte, bloqueo, etiqueta de color; posición (x,y,anchor / moveBy), tamaño (size / resize %), rotación, sesgo, volteo; orden (order/parent/above/below); color de una forma, trazo de forma, 'Mezclar si' (blendIf), máscara y efectos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
docNoDocumento (nombre o índice desde 1). Por defecto el activo.
fillNoRelleno (no afecta efectos de capa)
flipNo
maskNoMismos parámetros que ps_mask (sin layer)
nameNo
sizeNoTamaño final en px (si falta uno, mantiene proporción)
skewNo
aboveNoCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
belowNoCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
blendNoModo de fusión: normal, multiply, screen, overlay, softLight, hardLight, vividLight, linearLight, pinLight, hardMix, colorDodge, linearDodge, colorBurn, linearBurn, darken, lighten, darkerColor, lighterColor, difference, exclusion, subtract, divide, hue, saturation, color, luminosity, passThrough
labelNo
layerYesCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
orderNo
anchorNoPunto de la capa que se coloca en (x,y). Por defecto topleft
lockedNo
moveByNo
parentNoCapa: nombre, 'Grupo/Capa', id numérico o {id|name|path|index|nth}
resizeNoEscala en %
rotateNo
alignToNo
blendIfNoMezclar si (blend if)
clippedNoMáscara de recorte sobre la capa de abajo
effectsNoEfectos de capa con el mismo esquema que ps_layer_style.effects: {dropShadow:[{color,opacity,angle,distance,size,blend}], outerGlow:{color,opacity,size,noise,blend}, innerGlow, bevelEmboss, satin, colorOverlay, gradientOverlay:{stops,angle}, stroke:{size,position,color}, recipe:'nombre', raw, clear}
opacityNo
visibleNo
fillColorNoNuevo color de una capa de relleno/forma
effectsModeNo
shapeStrokeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden for a 30-parameter mutator. It discloses the scope of mutation ("casi todo") but nothing about permissions, prerequisites, reversibility, error behavior, or how conflicting options (e.g. size vs resize, x/y vs moveBy) interact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense semicolon-separated run-on. It is front-loaded with the verb and wastes no words on fluff, but the lack of structure makes a 30-parameter capability list hard to scan, and "casi todo" is needlessly vague.

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

Completeness2/5

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

For a 30-parameter tool with no annotations and no output schema, the description is inadequate: it never explains parameter interactions, prerequisites, or the expected result, leaving an agent unable to invoke it correctly in non-trivial cases.

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?

At 50% schema coverage, the description must compensate, and it partially does by grouping parameters logically (posición: x,y,anchor/moveBy; tamaño: size/resize; orden: order/parent/above/below). However, it adds no syntax or format detail beyond the schema and doesn't resolve ambiguities between the overlapping position/size parameters.

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 ("Cambia") and resource ("una capa") and then enumerates the modifiable properties, so an agent can quickly see this is the broad layer-mutation tool. It does not, however, explicitly distinguish itself from overlapping siblings like ps_align, ps_fill, or ps_mask, which also touch some of these same fields.

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?

There is no when-to-use guidance, no when-not-to-use, and no mention of alternatives. The agent is told what the tool *can* change but never when to prefer it over ps_align, ps_fill, ps_mask, or ps_layer_style, some of which clearly overlap.

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