Skip to main content
Glama

photoshop_expand_selection

Expand the active Photoshop selection outward by a specified number of pixels to grow a mask or selection area.

Instructions

Expand the active selection outwards by specified pixels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pixelsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so the description carries the full burden. It says selection expands but doesn't state what happens if no selection is active (error?), whether it requires an open document, whether the operation is undoable, or how it interacts with feathering. Minimal behavioral context for a mutation 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?

One sentence, front-loaded with the verb and resource, zero waste.

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?

Output schema exists so return values need not be explained. However, with no annotations and no error/precondition info, the description is minimally complete for a mutate-selection tool that requires an active selection.

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 0%, but the single parameter 'pixels' is semantically simple. The description says 'outwards by specified pixels' which adds the direction and unit meaning beyond the bare schema. Baseline 4 for zero params doesn't apply since there is one param; with 0% coverage a 3 reflects adequate but not rich specification (no range, no negative-value behavior).

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?

Names a specific verb (expand), resource (active selection), and direction/unit (outwards by specified pixels). Clearly distinguished from sibling photoshop_contract_selection which does the opposite.

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?

Implies usage by describing what it does, but gives no explicit when-to-use context or reference to the sibling contract/feather tools which are the natural alternatives.

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