Skip to main content
Glama
pixelvault-dev

@pixelvault-dev/local-mcp

Upload image

upload_image

Upload images to PixelVault using a local file path, public URL, or base64 data to receive a CDN URL. The URL supports on-the-fly transforms for resizing, cropping, format conversion, and AI background removal.

Instructions

Upload an image to PixelVault and get an instant CDN URL. Prefer path — a LOCAL file path the server reads off disk and streams — so large files aren't base64-encoded into the model context. Alternatively pass source_url (a public https URL the API imports) or data (base64 bytes). Optional folder, filename, visibility (private → signed URL, needs a secret key), expires_in (auto-expiring image), sign_expires_in. Max 5 MB; JPG/PNG/GIF/WebP/AVIF/SVG. The returned CDN URL supports on-the-fly transforms via query params — e.g. ?w=400&fit=cover (resize/crop), ?fmt=webp (format), ?segment=foreground (AI background removal → transparent PNG), and effects like ?blur=30&saturation=0&rotate=90. Or call transform_image to build a valid transform URL for you. See https://pixelvault.dev/docs#transforms.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoBase64-encoded image bytes (data URLs accepted). Prefer `path` for local files. Provide exactly one of path, source_url, or data.
pathNoAbsolute or relative path to a LOCAL image file. The server reads the file off disk and streams the bytes — nothing is base64-encoded into the model context, so large files work. Provide exactly one of path, source_url, or data.
folderNoOptional folder/path prefix for the image.
filenameNoOptional filename override, e.g. photo.png.
expires_inNoOptional time-to-live in seconds (60–2,592,000, i.e. 1 min to 30 days). The image is auto-deleted after this. Omit for a permanent image.
source_urlNoPublic https URL of an image; the PixelVault API fetches and imports it. Provide exactly one of path, source_url, or data.
visibilityNo`private` returns a signed URL only link-holders can open. Defaults to public.
sign_expires_inNoFor visibility=private: signed-URL lifetime in seconds (default 3600).
Behavior4/5

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

With no annotations, the description carries full burden. Discloses file size limit (5 MB), supported formats, auto-deletion with expires_in, private visibility yielding signed URLs, and on-the-fly transforms. Could mention overwrite behavior but very transparent overall.

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?

Well-structured with main action first, then parameter alternatives and optional fields. Slightly lengthy but every sentence adds value. Could be more concise by grouping transforms, but still efficient.

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?

Very complete: covers all 8 parameters, return value (CDN URL with transforms), explains transforms, mentions max size and formats, references external docs. No output schema or annotations, so description compensates fully.

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

Parameters5/5

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

Despite 100% schema coverage, description adds significant value: explains path reads local disk to avoid base64, source_url is fetched, data is base64, visibility meaning, and expires_in auto-deletion. Provides context far beyond schema descriptions.

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?

Clearly states 'Upload an image to PixelVault and get an instant CDN URL' with specific verb and resource. Distinguishes from siblings by discussing alternative input methods and mentioning transform_image for URL transformations.

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

Usage Guidelines4/5

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

Provides explicit guidance on parameter preference: 'Prefer path' for large files to avoid base64 encoding. Mentions alternative tool transform_image for building transform URLs. Lacks explicit when-not-to-use but sibling names imply distinct use cases.

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