Skip to main content
Glama
pixelvault-dev

@pixelvault-dev/local-mcp

Build transform URL

transform_image

Generate a CDN transform URL for PixelVault images to apply resize, crop, AI background removal, format/quality, and effects like blur, sharpen, rotate, flip, brightness/contrast/saturation, or watermark tiling.

Instructions

Build an on-the-fly transform URL for a PixelVault image (resize, crop, format/quality, AI background removal, blur/sharpen/rotate/flip, brightness/contrast/saturation, and same-project watermark tiling). Provide exactly one of url (a PixelVault CDN URL) or id (resolved via the API), plus one or more transform params. See https://pixelvault.dev/docs#transforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPixelVault image id (e.g. img_abc123); its CDN URL is resolved via the API. Provide this OR url.
fitNoResize mode. scale-down (default) never enlarges; others may upscale. Only with width/height.
urlNoAbsolute PixelVault CDN URL (as returned by upload_image / get_image / list_images). Provide this OR id.
blurNoGaussian blur (0-250).
flipNoMirror horizontally (h), vertically (v), or both (hv).
sizeNoNamed size preset: s=256px, m=640px, l=1280px, social=1200x630 OG card. Wins over width/height.
tileNoFilename of another image in the SAME project to tile as a watermark.
zoomNoFace-crop tightness 0.0-1.0, only with gravity=face.
widthNoTarget width in px (1..4000).
formatNoOutput format. auto negotiates WebP/AVIF.
heightNoTarget height in px (1..4000).
rotateNoRotate clockwise; rounded to the nearest right angle.
gravityNoCrop anchor with fit=cover|crop: face, left, right, top, bottom, auto, or 'XxY'.
qualityNoOutput quality. auto lets Cloudflare choose.
segmentNoAI background removal: foreground keeps the subject, background becomes transparent (PNG output).
sharpenNoSharpen strength (0-10).
contrastNoContrast multiplier 0-2 (1=no change).
backgroundNoFill color behind a removed/padded background: hex, rgb(), or CSS name.
brightnessNoBrightness multiplier 0-2 (1=no change).
saturationNoSaturation multiplier 0-2 (1=no change, 0=grayscale).
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It mentions 'on-the-fly' and 'resolved via the API' but does not explicitly state side effects, whether the tool makes network calls, or any rate limits. The behavior is moderately clear.

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 a single sentence with a brief instruction and a link. It is front-loaded with the core purpose and contains no fluff.

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

Completeness4/5

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

With 20 parameters and no output schema, the description adequately lists capabilities and constraints. The return value (URL string) is implied but not explicitly stated. Overall, it is fairly complete.

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?

Schema description coverage is 100%, so baseline is 3. The description adds value by grouping parameters into categories (resize, crop, etc.) and highlighting the exclusive-or relationship between url and id.

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?

The description clearly states the tool builds a transform URL for PixelVault images, listing many operations. It is distinct from sibling tools like upload_image or list_images.

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?

The description provides a key usage constraint (provide one of url or id) but does not explicitly state when to use this tool versus alternatives, such as signing vs. transforming.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pixelvault-dev/mcp-local'

If you have feedback or need assistance with the MCP directory API, please join our Discord server