Skip to main content
Glama

photoshop_content_aware_fill

Fill a selected area in Photoshop using Content-Aware Fill to remove distractions or repair imperfections by intelligently analyzing surrounding pixels.

Instructions

Fill the active selection using Content-Aware Fill.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure, and it says almost nothing: it does not state that pixel content is destructively modified, whether the operation is undoable, or what happens if no selection is active. For a mutation tool with zero annotation coverage, more is required.

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?

A single front-loaded sentence with no filler. It is appropriately sized for the tool's simplicity, though it is on the terse side rather than fully economical-plus-informative.

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?

The tool has no parameters and an output schema exists, so return values need no explanation. However, the operational preconditions (a non-empty selection) and the destructive nature of the fill are missing, which leaves the definition only minimally adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; per the baseline, a parameter-free tool scores 4. The description correctly does not invent parameter discussion.

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 and resource ('Fill the active selection') plus the mechanism ('using Content-Aware Fill'), so it is distinguishable from generic fills. It stops short of explicitly differentiating itself from the closely related siblings photoshop_generative_fill_ai and photoshop_smart_remove_distractions, which is the one ambiguity an agent faces here.

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?

Mentioning 'the active selection' implies a selection must exist first, but there is no explicit when-to-use guidance, no statement of the alternative (generative_fill_ai) and no condition that selects between them. The agent must infer usage purely from the name.

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