Skip to main content
Glama
Immersive-Media-Technologies

Photoshop-MCP-IMT

by Immersive-Media-Technologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

photoshop_select_rectangle

Create a rectangular pixel selection from corner coordinates to mask, crop a region, or prepare a layer mask. Combine it with the current selection using replace, add, subtract, or intersect modes.

Instructions

Create a rectangular pixel selection from corner coordinates.

Use when: masking, cropping a region, or preparing for layer mask. Do NOT use when: subject isolation is needed — use photoshop_recipe_remove_background.

Returns: selection bounds [left, top, right, bottom]. Preconditions: active document. Side effects: replaces, adds, subtracts, or intersects the current selection. mode intersect/add/subtract uses Action Manager and does not depend on the SelectionType enum.

Input Schema

NameRequiredDescriptionDefault
topYesTop edge in pixels
leftYesLeft edge in pixels
modeNoHow this rectangle combines with the current selection. Default replace. Use intersect when SelectionType.INTERSECT is unavailable.
rightYesRight edge in pixels
bottomYesBottom edge in pixels
document_idNoOptional Photoshop document id from photoshop_get_state / photoshop_list_documents. When set, the tool activates that document before running so a UI tab switch cannot retarget the edit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are present, but the description takes on the burden: it discloses the precondition (active document), the selection-combination side effects, and an implementation nuance about mode handling. Nothing about the tool's mutating behavior is hidden.

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?

The description is compact and front-loaded: purpose, when/when-not, returns, preconditions, and side effects are each one clear line. No filler or redundant restatement of the name or schema.

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

Completeness5/5

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

With no output schema, the description states the return format; with no annotations, it states preconditions and side effects. Combined with 100% schema coverage, an agent has all the information needed to invoke this tool correctly and safely.

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?

Input schema covers 100% of the 6 parameters, so the schema already carries the load. The description adds a small amount of extra context (corners vs edges, mode implementation) but does not substantially enrich parameter meaning beyond the schema.

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?

Opens with a specific verb and resource: 'Create a rectangular pixel selection from corner coordinates.' This clearly distinguishes it from sibling selection tools (select_ellipse, select_all, select_subject) and from crop_document, and the returns line states the exact output shape.

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

Usage Guidelines5/5

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

The description explicitly gives use cases ('masking, cropping a region, or preparing for layer mask') and names the exact alternative when not to use it ('subject isolation... use photoshop_recipe_remove_background'). An agent can decide between tools without opening schemas.

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

Deploy Server

Other Tools