Cavi Adobe Authoring MCP

by cavi-ai

Overview Schema Source Related Servers Discussions Admin

Python

Local

adobe_resize_image

Destructive

Resize an owned Photoshop PSD to exact pixel dimensions while preserving editable layers and paths.

Instructions

Resample an owned Photoshop PSD to pixel dimensions while retaining editable layers and paths.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application": "<application>",
      "session_id": "<session_id>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "adobe_resize_image"
  }
}

Input Schema

Name	Required	Description	Default
`width`	Yes
`height`	Yes
`session_id`	Yes
`application`	Yes

Output Schema

Name	Required	Description	Default
`copy`	Yes
`document`	Yes
`retry_safe`	Yes
`session_id`	Yes
`operation_id`	Yes
`source_sha256`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.0Nov 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real value by stating that editable layers and paths are retained, which is a behavioral guarantee not visible in the schema. However, it omits the lossy/irreversible nature of resampling and the 2880 px ceiling that makes the operation destructive in practice.

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?

A single sentence that leads with the action and ends with the preservation guarantee. No filler, nothing to cut.

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?

An output schema exists, so return values need no explanation, and the tool is structurally simple. Still, with four required parameters at 0% schema coverage, the description leaves the session_id requirement and aspect-ratio behavior undefined for an agent trying to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only restates that dimensions are in pixels. Nothing explains session_id provenance, whether aspect ratio is preserved when both width and height are required, or how the application const interacts with the call.

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?

Specific verb ("Resample") plus specific resource ("an owned Photoshop PSD") and outcome ("pixel dimensions"). It distinguishes itself from siblings like adobe_export or adobe_place_image by operating on an already-owned document, though no sibling is named explicitly.

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?

"Owned" implies a prerequisite (the PSD must already be open via a copy/session), which is implicit usage guidance. There is no explicit when-to-use vs. alternatives statement and no mention of when this is inappropriate (e.g., for non-owned or non-PSD assets).

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

Deploy Server