Skip to main content
Glama

Colocar imagen

ps_place_image

Place an image file into Photoshop as an embedded or linked smart object, fit it into a frame with cover, contain, or stretch, round corners, and set scale or position.

Instructions

Coloca un archivo como objeto inteligente (incrustado o vinculado). Con box={x,y,width,height} y fit ('cover' recorta con máscara, 'contain', 'stretch') la encaja en un marco; radius redondea el marco. También escala/posición libres.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNo
yNo
boxNo
docNoDocumento (nombre o índice desde 1). Por defecto el activo.
fitNo
urlNoURL de la imagen (se descarga a una carpeta temporal)
fillNoRelleno (no afecta efectos de capa)
nameNo
pathNoRuta local
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
scaleNo% si no usas box
widthNo
anchorNoPunto de la capa que se coloca en (x,y). Por defecto topleft
heightNo
linkedNoVinculado en vez de incrustado
parentNoGrupo donde crearla
radiusNo
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}
offsetXNo
offsetYNo
opacityNo
visibleNo
rotationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations, so the description must carry the behavioral load. It usefully discloses that 'cover' crops with a mask, that it can be embedded or linked, and that it accepts a url (downloaded) or path. But for a 27-parameter mutation tool it stays silent on permissions, reversibility, effects/mask interactions, and most side effects.

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?

Three compact sentences, front-loaded with the core capability and then the framing options. Every clause carries meaning; no filler. Slightly terse given the parameter surface but not bloated.

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 27-parameter, zero-required, no-annotation, no-output-schema tool with nested objects, the description is far too sparse. Large functional areas (blend modes, layer effects recipe, clipping, grouping, visibility/opacity) are entirely undiscussed, leaving the agent to guess at intended use.

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 48%, below the 50% mark, so the description should compensate. It meaningfully explains box, fit (including cover's mask behavior), and radius, but the majority of parameters (blend, effects, anchor, clipped, linked, parent, opacity, offsets, rotation) get no meaning beyond the schema.

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+resource: places a file as a smart object (embedded or linked), and mentions box-fitting, radius, and free scale/position. This is clearly a placement tool, not shape/text/layer creation. However, it never distinguishes itself from the sibling ps_smart_object, leaving the boundary to inference.

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 when-to-use or when-not guidance. It implies you can use box+fit to frame, or scale/position freely, but never says which mode suits which scenario, nor when to prefer linked vs embedded, nor when to use this instead of ps_smart_object.

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